Re: Why are new package versions depending on libc6 in unstable?

To: debian-devel@lists.debian.org
Subject: Re: Why are new package versions depending on libc6 in unstable?
From: Joey Hess <joeyh@debian.org>
Date: Tue, 19 Nov 2002 12:02:24 -0500
Message-id: <[🔎] 20021119170224.GB5320@dragon.kitenet.net>
Mail-followup-to: debian-devel@lists.debian.org
In-reply-to: <[🔎] 20021119065911.GA30228@evbergen.xs4all.nl>
References: <[🔎] 20021119013357.GA3397@dragon.kitenet.net> <[🔎] Pine.LNX.3.96.1021118205909.5937A-100000@wakko.debian.net> <[🔎] 20021119052124.GB23895@misery.proulx.com> <[🔎] 20021119065911.GA30228@evbergen.xs4all.nl>

Emile van Bergen wrote:
> Whatever happened to: minor version number change - binary compatible,
> major version number change - source compatible or not compatible at all?

Versioned symbols and stated goals of never having libc7, ever.

-- 
see shy jo

Attachment: pgplhGirEsodH.pgp
Description: PGP signature

Reply to:

References:
- Re: Why are new package versions depending on libc6 in unstable?
  - From: Joey Hess <joeyh@debian.org>
- Re: Why are new package versions depending on libc6 in unstable?
  - From: Jason Gunthorpe <jgg@debian.org>
- Re: Why are new package versions depending on libc6 in unstable?
  - From: bob@proulx.com (Bob Proulx)
- Re: Why are new package versions depending on libc6 in unstable?
  - From: Emile van Bergen <emile-deb@evbergen.xs4all.nl>

Prev by Date: Re: Why are new package versions depending on libc6 in unstable?
Next by Date: the ghdl bomb
Previous by thread: Re: Why are new package versions depending on libc6 in unstable?
Next by thread: Re: Why are new package versions depending on libc6 in unstable?
Index(es):
- Date
- Thread