Bug#167292: ITP: libc12 -- NetBSD C library

2002-10-31 Thread Joel Baker
Package: wnpp
Version: N/A; reported 2002-10-31
Severity: wishlist

* Package name: libc12
* Version: 1.6+debian.1
* Upstream Author: The NetBSD Foundation
* URL: http://www.netbsd.org/
* License: Varies per source file; see discussion on debian-legal

* Package: libc12
Description: NetBSD C library: Shared libraries
 Contains the standard libraries that are used by nearly all programs
 on the system. This package includes shared versions of the standard C
 library and the standard math library, as well as many others.

* Package: libc12-dev
Description: NetBSD C library: Development Libraries and Header Files
 Contains the symlinks, headers, and object files needed to compile and
 link programs which use the standard C library.

* Package: libc12-dbg
Description: NetBSD C library: Development Libraries and Header Files
 Contains unstripped shared libraries.
 This package is provided primarily to provide a backtrace with
 names in a debugger, this makes it somewhat easier to interpret core
 dumps. The libraries are installed in /usr/lib/debug and can be
 used by placing that directory in LD_LIBRARY_PATH.
 Most people will not need this package.

* Package: libc12-pic
Description: NetBSD C library: PIC archive library
 Contains an archive library (ar file) composed of individual shared objects.
 This is used for creating a library which is a smaller subset of the
 standard libc shared library. The reduced library is used on the Debian
 boot floppies. If you are not making your own set of Debian boot floppies
 using the `boot-floppies' package, you probably don't need this package.

* Package: libc12-prof
Description: NetBSD C library: Shared libraries
 Static libraries compiled with profiling info (-pg) suitable for use with
 gprof.



pgpn3B2rkzTfa.pgp
Description: PGP signature


Bug#167292: ITP: libc12 -- NetBSD C library

2002-11-01 Thread Joel Baker
On Fri, Nov 01, 2002 at 10:26:06AM +0900, GOTO Masanori wrote:
> At Thu, 31 Oct 2002 15:54:34 -0700,
> Joel Baker wrote:
> > * Package name: libc12
> > * Version: 1.6+debian.1
> > * Upstream Author: The NetBSD Foundation
> > * URL: http://www.netbsd.org/
> > * License: Varies per source file; see discussion on debian-legal
> 
> I recommend "netbsd-libc" or "netbsd-libc12".
> 
> There is already "libc6" (glibc). The name "libc12" is similar to
> "libc5" or "libc6" which are GNU libc. It leads a bit confusion.  I
> don't intend to prioritize GNU libc, because GNU libc does not use
> their source package name as "libc", but "glibc".
> 
> Besides imagine if FreeBSD's libc or other BSD libc is ITP-ed.
> Distinguishing their name apparently is a good idea, for example
> "diet-libc".
> 
> BTW, what does "12" of libc12 mean?

I will be happy to name the binaries netbsd-libc12 when the current libc6
becomes gnu-libc6 or glibc6; certainly the source package name might
change, but since there are exactly 0 platforms which will ever have both
GNU libc and NetBSD libc (they are exclusive and must be separated by arch,
since binaries depend on one or other other), it is simpler to have the
binary packages named consistantly. FreeBSD's is libc4, though they are
using GNU libc instead; the Hurd has libc0.2 as their package name.

(Note that I would, in fact, be quite happy if all libc packages were more
specific; until then, however, all known examples do in fact call the
binary libc*, where * is the major version number, per Policy).
-- 
Joel Baker
[EMAIL PROTECTED]


pgp9l51AM1F6w.pgp
Description: PGP signature


Bug#167292: ITP: libc12 -- NetBSD C library

2002-11-01 Thread GOTO Masanori
At Thu, 31 Oct 2002 15:54:34 -0700,
Joel Baker wrote:
> * Package name: libc12
> * Version: 1.6+debian.1
> * Upstream Author: The NetBSD Foundation
> * URL: http://www.netbsd.org/
> * License: Varies per source file; see discussion on debian-legal

I recommend "netbsd-libc" or "netbsd-libc12".

There is already "libc6" (glibc). The name "libc12" is similar to
"libc5" or "libc6" which are GNU libc. It leads a bit confusion.  I
don't intend to prioritize GNU libc, because GNU libc does not use
their source package name as "libc", but "glibc".

Besides imagine if FreeBSD's libc or other BSD libc is ITP-ed.
Distinguishing their name apparently is a good idea, for example
"diet-libc".

BTW, what does "12" of libc12 mean?

Regards,
-- gotom




Bug#167292: ITP: libc12 -- NetBSD C library

2002-11-01 Thread Junichi Uekawa
At Thu, 31 Oct 2002 23:54:10 -0700,
Joel Baker wrote:
> 
> > BTW, what does "12" of libc12 mean?
> 
> I will be happy to name the binaries netbsd-libc12 when the current libc6
> becomes gnu-libc6 or glibc6; certainly the source package name might
> change, but since there are exactly 0 platforms which will ever have both
> GNU libc and NetBSD libc (they are exclusive and must be separated by arch,
> since binaries depend on one or other other), it is simpler to have the
> binary packages named consistantly. FreeBSD's is libc4, though they are
> using GNU libc instead; the Hurd has libc0.2 as their package name.

ITP should state the name of the source package.

Hence, I think your ITP should have said something like, "source
package netbsd-libc, which builds a binary package libc12."




regards,
junichi



Bug#167292: ITP: libc12 -- NetBSD C library

2002-11-02 Thread Joel Baker
On Sat, Nov 02, 2002 at 10:59:10AM +0900, Junichi Uekawa wrote:
> At Thu, 31 Oct 2002 23:54:10 -0700,
> Joel Baker wrote:
> > 
> > > BTW, what does "12" of libc12 mean?
> > 
> > I will be happy to name the binaries netbsd-libc12 when the current libc6
> > becomes gnu-libc6 or glibc6; certainly the source package name might
> > change, but since there are exactly 0 platforms which will ever have both
> > GNU libc and NetBSD libc (they are exclusive and must be separated by arch,
> > since binaries depend on one or other other), it is simpler to have the
> > binary packages named consistantly. FreeBSD's is libc4, though they are
> > using GNU libc instead; the Hurd has libc0.2 as their package name.
> 
> ITP should state the name of the source package.
> 
> Hence, I think your ITP should have said something like, "source
> package netbsd-libc, which builds a binary package libc12."

At the time, it was source-titled 'libc12' as well. I concur, however,
with the thought of renaming the source to netbsd-libc, and the package
as it stands (that is, the one in the Debian-BSD archive, and which will
be uploaded to the main archive once netbsd-* arch sections exist) is now
source-named netbsd-libc.
-- 
***
Joel Baker   System Administrator - lightbearer.com
[EMAIL PROTECTED]  http://users.lightbearer.com/lucifer/