Debian Developers - Re: General Resolution: Force AMD64 into Sarge

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > July 2004 > Re: General Resolution: Force AMD64 into Sarge





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: General Resolution: Force AMD64 into Sarge
Andreas Metzler

2004-07-23, 2:50 am

On 2004-07-23 Adam Majer <adamm@galacticasoftware.com> wrote:
[...]
> The biggest problem with Sarge might be the last of AMD64 support. I
> do not think it is best for us to wait another two years for AMD64
> to get to stable. I'd rather wait another 3-4 months for Sarge
> *with* amd64.


I cannot agree wholeheartedly to that. Being in a pre-release status
for extended periods of time is difficult. - The necessary freeze of
at least base makes work for maintainers of base packages very
hard, necessary changes are postponed farther and farther. - Base
dependencies have already been frozen for 4 months.

Take for example gcrypt: We are still using libgcrypt7 for gnutls,
because gcrypt 1.2, the first stable release, was released 2004-04-15,
after the base system freeze.

And being in limbo about the time frame is the worst problem of any
release, "We are waiting for XXX anyway, so I can upload new upstream
Y" (which will break two other packages, block testing migration for
a month, whatever.)
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2009 webservertalk.com