[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Glibc Packaging Issues



There are several issues that need to be resolved before I can package
glibc.  Here is my current list of issues, in no particular order.
Please take a look at them and offer any advice you may have.  My
current preferences are in braces ([]).

1. Should the main packages be called glibc2* or libc6*?  [Undecided]

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]

3. Glibc uses NSS.  Which package should probide the
/etc/nsswitch.conf file?  [base-files]

4. Glibc provides the locale and localedef programs and the locale
data files.  How should these be packaged?  [New locale package?]

5. Glibc provides the rpcgen and rpcinfo programs.  Should these
replace the versions already in the netstd package?  [No]

6. Glibc provided the ypcat, ypmatch, ypwhich, yppoll and ypset
programs.  Should these replase the versions in the nis package?  [No]

7. Glibc provides the zdump and zic programs and the timezone data
files.  Should glibc take over the existing timezone package?
[Probably]

8. Glibc provides the /etc/rpc file.  Should this replace the version
in the netbase package?  [No]

9. Glibc is really a collection of several libraries, including crypt,
db, nsl, pthread, resolv, rpcsvc.  Should these be packaged
separately?  [Probably not]

10. Should profiling versions of libraries be packaged.  [Undecided]

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: