> Of cource, there isn't such a list now (as far as I know, at least I
> guess that list would be empty now).
>
> > Anyways, Debian just can't compete with commercial distributions which can
> > allow to suppose that they are self-contained. Debian is NOT. Unlike
> > RedHat (which has, for instanc
> > > I'm not entirely certain I see why we need to remove libc5 packages from
> > > the system for Debian 2.0. While I agree that the primary packages should
> > > really be glibc, I don't see how a few lib5 packages are going to hurt the
> > > distribution
> >
> > Well, they won't hurt much, bu
> > I'm not entirely certain I see why we need to remove libc5 packages from
> > the system for Debian 2.0. While I agree that the primary packages should
> > really be glibc, I don't see how a few lib5 packages are going to hurt the
> > distribution
>
> Well, they won't hurt much, but they would
> > Yes, they should be. When do we remove all the non-libc6 packages, though?
>
> I'm not entirely certain I see why we need to remove libc5 packages from
> the system for Debian 2.0. While I agree that the primary packages should
> really be glibc, I don't see how a few lib5 packages are going
> "BW" == Brian White <[EMAIL PROTECTED]> writes:
:: * July 15th: All libraries *must* be libc6.
:: * July 31th: All packages must be libc6.
What about:
* June 30th: Bug reports on all non-libc6 libraries.
* July 15th: All libraries libc6 compatible.
* July 31th: Bug reports on all l
> > Do we also want to remove all libc5 dependant packages at some point? I
> > think this would be a good idea since otherwise things are going to get
> > pretty messed up. We might want to do all three immediately.
>
> * all packages should be libc6 when "hamm" is frozen. (later?)
Yes, they s
-BEGIN PGP SIGNED MESSAGE-
On Fri, 13 Jun 1997, Brian White wrote:
> > > Do we also want to remove all libc5 dependant packages at some point? I
> > > think this would be a good idea since otherwise things are going to get
> > > pretty messed up. We might want to do all three immediatel
On Thu, 12 Jun 1997, Brian White wrote:
> > * July 15th: All libraries *must* be libc6.
> > * July 31th: All packages must be libc6.
>
> That's fine with me. I figure requiring packages only libc6 will also put
> a lot of pressure on library maintainers to get things done.
>
> Do we also want t
> > I'd like to set a date after which all new uploads must be libc6. How
> > does July 31st sound?
>
> I'd like to have 2 different dates:
> - 1st deadline for libraries.
> - 2nd deadline for other packages.
>
> That could make something like:
>
> * July 15th: All libraries *must* be libc6.
>
On Thu, 12 Jun 1997, Brian White wrote:
> > > What is the policy for uploads into unstable regarding libc6?
> > > Must all new programs goint into unstable be linked with libc6?
> >
> > Since Debian 2.0 is meant to be a libc6 system, the answer is yes. Of
> > course, if the libraries that the p
> > What is the policy for uploads into unstable regarding libc6?
> > Must all new programs goint into unstable be linked with libc6?
>
> Since Debian 2.0 is meant to be a libc6 system, the answer is yes. Of
> course, if the libraries that the program depends on are not yet
> available for libc6,
On 9 Jun 1997, Milan Zamazal wrote:
> > "GM" == Guy Maor <[EMAIL PROTECTED]> writes:
>
> GM: David Frey <[EMAIL PROTECTED]> writes:
> :: Must all new programs goint into unstable be linked with libc6?
>
> GM: Since Debian 2.0 is meant to be a libc6 system, the answer is yes.
>
>
> That's why we have the altgcc and the altdev packages. You'll still
> be able to compile libc5 programs by just putting
> /usr/i486-linuxlibc1/bin first in your path.
Just a note to one thing where this doesn't work: Some programs use
-I/usr/include/bsd on the command line to get BSD behaviour
>I didn't meant to imply that libc5 packages will be
>rejected.
Ok, thanks for clearing that up :-)
--
Thomas Koenig, [EMAIL PROTECTED], [EMAIL PROTECTED]
The joy of engineering is to find a straight line on a double
logarithmic diagram.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word
[EMAIL PROTECTED] (J.H.M.Dassen) writes:
> A) "Debian 2.0 will be a libc6 system, so it is desirable for packages going
>into unstable to be linked against libc6 as soon as possible"
Yes, I meant A. I didn't meant to imply that libc5 packages will be
rejected.
Guy
--
TO UNSUBSCRIBE FROM
Milan Zamazal <[EMAIL PROTECTED]> writes:
> Well, if I install libc6 now, wouldn't it break compilation of some
> programs? I'm dependent on my Debian machine, so I can't perform too
> hard experiments with it.
That's why we have the altgcc and the altdev packages. You'll still
be able to compi
> "GM" == Guy Maor <[EMAIL PROTECTED]> writes:
GM: David Frey <[EMAIL PROTECTED]> writes:
:: Must all new programs goint into unstable be linked with libc6?
GM: Since Debian 2.0 is meant to be a libc6 system, the answer is yes.
Well, if I install libc6 now, wouldn't it break comp
On Jun 8, Guy Maor wrote
> David Frey <[EMAIL PROTECTED]> writes:
> > What is the policy for uploads into unstable regarding libc6?
> > Must all new programs goint into unstable be linked with libc6?
>
> Since Debian 2.0 is meant to be a libc6 system, the answer is yes. Of
> course, if the librar
Thomas Koenig <[EMAIL PROTECTED]> writes:
> Guy Maor wrote:
>
> >> Must all new programs goint into unstable be linked with libc6?
> >
> >Since Debian 2.0 is meant to be a libc6 system, the answer is yes.
>
> If this is indeed a requirement, at is now orphaned.
Surely you don't have to jump to
Guy Maor wrote:
>> Must all new programs goint into unstable be linked with libc6?
>
>Since Debian 2.0 is meant to be a libc6 system, the answer is yes.
If this is indeed a requirement, at is now orphaned.
--
Thomas Koenig, [EMAIL PROTECTED], [EMAIL PROTECTED]
The joy of engineering is to find a
David Frey <[EMAIL PROTECTED]> writes:
> What is the policy for uploads into unstable regarding libc6?
> Must all new programs goint into unstable be linked with libc6?
Since Debian 2.0 is meant to be a libc6 system, the answer is yes. Of
course, if the libraries that the program depends on are
21 matches
Mail list logo
