Re: Glibc Packaging Issues
Mark Eichin writes:
> > 9. Glibc is really a collection of several libraries, including crypt,
> > db, nsl, pthread, resolv, rpcsvc. Should these be packaged
> > separately? [Probably not]
>
> If you supply libdb, be sure to "replace:" the libdb package.
Only libdb1-dev needs to be replaced. The libdb1 run-time package
doesn't conflict.
> As for pthread: this is LinuxThreads, right? (I'm curious about
> coexistence with Proven's posix threads, but only mildly...)
Yes, it is LinuxThreads. I don't think anyone intends to use MIT
pthreads anymore.
> > 2. Glibc provides the gencat, getconf and makedb programs. Should
> > these go in the libc6 package, a separate libc6-bin package, some
> > other package or nowhere? [Undecided]
>
> * gencat is for message catalog stuff, right? libc6-dev.
Yes.
> * Is makedb the shell script from the db hash tests?
> (libdb/tests/hash.test/makedb.sh, that is) if so, don't install it
> anywhere, it is (1) a trivial script (2) not useful outside of the
> test suite.
This makedb is a C program. As far as I can tell, it converts a
simple text file to a db file. I don't think it's necessary, but I'll
try to find out.
> * getconf - don't know what it is, sorry.
Neither do I.
> > 3. Glibc uses NSS. Which package should probide the
> > /etc/nsswitch.conf file? [base-files]
>
> Also be sure that the NIS package has some postinst option to
> automatically set that up correctly (and that the default does *not*
> use NIS :-)
Are you listening Miquel? :)
David
--
David Engel Optical Data Systems, Inc.
david@ods.com 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: