Re: Bug#43928: libc and kernel source policy
Hi,
>>"Paul" == Paul Wade <paulwade@greenbush.com> writes:
Paul> Recently I built the latest X for slink and did so by installing
Paul> kernel-headers (2.2.12) and the "legacy" symlinks for
Paul> /usr/include/(asm,linux). Seems X needed some constants for support of
Paul> newer hardware.
First: you are now one amongst a handful of people who have
compiled their won X system. People who can do that know how to get
newer kernel header files, as they need them, and you are talking
here about the very tail end of the bell curve.
Paul> Do we assume that people only compile things on unstable
Paul> systems?
No. But you are asking for headers that are not provided on
Debian's stable system -- if you are looking for support for hardware
or software not shipped with slink, you may reasonably expect to have
to upgrade to unstable for native support; or else hack, like you
did.
Paul> If policy can't cover the variety of situations properly, it
Paul> should be weakened to at least allow easier solutions.
Nothing covers all situations completely. You want policy to
now cater to people building arcane software (yes, building X
is still arcane) with support for newer devices not released when
stable was released, and yet not wanting to upgrade to unstable?
I am afraid I do not find that reasonable.
Paul> I acknowledge that my systems are no longer "stable" if we use a strict
Paul> definition of the term.
BINGO!!!!!!
Paul> However, I do believe that we are trying to deliver something
Paul> different from a Gateway PC preloaded with W98, Office, IE, and
Paul> a few games.
We are also not trying to create a policy that pleases
everyone all the time.
Paul> Does adhering to a policy diminish the usefulness of the
Paul> system? This should always be seriously considered.
It was. We were really concerned about the instability you
introduced and dismissed so cavalierly, knowing that the handful of
people who really needed newer kernel headers, and knew enough of the
dangers introduced by a mismatched libc, would also know enough to
handle the situation.
I contend that anyone who does not know their way around
creating a simple symlink should be thanking the Debian policy.
manoj
--
If your life was a horse, you'd have to shoot it.
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: