Re: What is with the kernel maintainer? (How not to close Bug#147077)

[brian@debian.org (Brian Mays)]

Brian Mays wrote:

> > > I built a custom kernel using "make-kpkg".  I also built a
> > > pcmcia-modules package to accompany this kernel.  When I try to
> > > install this package, the following errors result from file
> > > conflicts: ... [example omitted]

Herbert Xu <herbert@gondor.apana.org.au> replied:

> > You shouldn't include PCMCIA modules in your kernel-image if you
> > intend to install it with pcmcia-modules. -

Agustín Martín Domingo <agmartin@aq.upm.es> asked:

> Do appropiate diversions help about that?

Diversions would be a nightmare to setup and maintain, but that's beside
the point.  Diversions should not be considered because the symlinks
causing the conflicts are NOT NECESSARY in the first place.  They
currently serve no purpose other than to complicate the PCMCIA init
script.

The two sets of modules are already located in different locations.
Unfortunately, the kernel source makes a series of symlinks to the
location where the stand-alone pcmcia modules reside.  These symlinks
(which have not been necessary for a long, long time -- i.e., before the
release of 2.4.1) are the source of the conflicts.

What I cited above is simply an example of what many users will do
because they don't know any better.  As a result, they will complain to
me.  This is why I want the symlinks (or rather the code that creates
them) removed.

Thanks for the suggestion anyway.

- Brian


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