At Fri, 12 Mar 2004 23:34:21 +0900, GOTO Masanori wrote: > At Tue, 24 Feb 2004 16:51:59 +0000, > Steve McIntyre wrote: > > On Tue, Feb 24, 2004 at 11:46:39AM -0500, Joey Hess wrote: > > >Steve McIntyre wrote: > > >> No problem here. The zone info is actually quite small (compressed) > > >> within the .deb, not really big enough to warrant the split I was > > >> (mistakenly) asking for. Sorry for bothering you and thanks for > > >> looking into this. > > > > > >It is, however, 5 mb unpacked, which is quite large compared to the > > >overall size of the debian base system. > > > > True. On a really small system that will hurt. > > > > >> Joey, where is the existing bug asking for the split? I can't find it > > >> in a quick check through the BTS... > > > > > >I can't find it, it may have been only a post to the debian-glibc > > >mailing list. > > > > OK, that explains it. > > > > Is it worth some discussion on debian-devel here to see what other > > people think? > > I welcome patches everytime. At least I don't have any plans to split > them.
Hm, I change my mind. The reason is: - Even if /usr/share/zoneinfo is not existed, an application should still work well. - Release interval is usually long: but timezone will be updated in each quarter. Sometimes it should update after releasing stable distro. But the current glibc does not update in woody. I plan to update glibc even stable distro to fix serious breakage (for example ia64 stack issue) and timezone update after sarge. - Actually almost all users use timezone info, but there is one user (Joey) to want to use non-timezone machine. I think it's rare case, though. - Yes, exactly 5MB would hurt on some small systems. In addition, I think even it's ok to split libc6 into two packages which are separatered with /lib part and /bin part (think about the current lib64 issue). So I become to agree with this thing as "ok" to put this kind of separation for zoneinfo. Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
