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

Re: 2.4.0!



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Christoph" == Christoph Lameter <christoph@lameter.com> writes:

    Christoph> Maybe we could make a distinction between

    Christoph> 1. Upstream software (which has already gone through a
    Christoph> lot of testing upstream and sidestreams in RH, SUSE
    Christoph> etc). It is highly unlikely that such software will
    Christoph> contain major bugs. There could be configuration
    Christoph> problems.

I'll add 3. here:

3. Upstream bugfix releases... like the just-released gtk 1.2.8 that
   will *not* happen to appear in potato.  Which really is a shame...

    Christoph> 2. Debian native software which needs extensive
    Christoph> testing. This would include debconf, packaging tools,
    Christoph> boot floppies, special scripts and other native
    Christoph> packages. Native software might only be testing within
    Christoph> Debian and is therefore much more fragile.

There's also a big difference between packages that only depend on
others and packages that have many others depend on 'em.  The former
doesn't break a lot usually (okay, breakage in a webserver like Apache
is a lot more important than breakage in s.th. as unfinished as
Abiword (IMHO)).  The latter can break many things...

I do think re-evaluating this would make sense... if we *want* to.

Oh, and not discouraging (or even flaming) people who do s.th. like
Slink-and-a-half would help a lot too... (I still can't fathom why
this went as it went... and where it *is* (knghtbrd's right))

Bye, J

- -- 
Jürgen A. Erhard      eMail: jae@ilk.de      phone: (GERMANY) 0721 27326
     MARS: http://members.tripod.com/Juergen_Erhard/mars_index.html
           "Outside of a dog, a man's best friend is a book;
           inside of a dog, it's very dark." --  Groucho Marx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Use Mailcrypt and GnuPG <http://www.gnupg.org/>

iEYEARECAAYFAjkumecACgkQN0B+CS56qs28sgCeO8Sw32rHY0UyWvY8mlo4f4+G
jvAAnipPM5iflmnKLZjjlvmNxOWzip4O
=yT76
-----END PGP SIGNATURE-----



Reply to: