Re: [gentoo-dev] Policy on kernel module ebuilds, etc

[John Nilsson]

Sounds fair enough. However, I think portage would do better not
creating symliks at all, just page the admin with na ewarn or einfo
message at mergetime...

/John

On Thu, 2004-02-12 at 07:25, Peter Johanson wrote:
> On Thu, Feb 12, 2004 at 07:01:57AM +0100, John Nilsson wrote:
> > what about /usr/src/linus-beta?
> >
> /usr/src/linux-beta is a convension that was added to "match" the
> /usr/src/linux convension from 2.4 kernels. Ultimately, it gets ugly
> doing things like having a configurable "Look here, no wait look here!"
> method for figuring out which kernel tree symlinks to use.
>
> Consider /usr/src/linux-beta a convenient symlink to have around, but
> portage will always be using /usr/src/linux for the say in how things
> get handled. Once it looks at /usr/src/linux, it can then figure out
> whether it's dealing with a 2.4 or a 2.6 kernel and go from there.
>
> -pete
>
> > -John
> >
> > On Thu, 2004-02-12 at 03:44, Peter Johanson wrote:
> > > hey all,
> > >
> > > in my work on bug #32737 for external module compilation, i've come
> > > upon one or two instances of problems with kernel module ebuilds. Wanted
> > > to shoot out a quick reminder/announcement about it.
> > >
> > > Kernel module ebuilds should *always* pull their information from
> > > /usr/src/linux/ and not from using `uname` or looking in /proc, etc.
> > > Ebuilds need to remain as "location agnostic" as possible so that liveCD
> > > building and other things people might be doing do not affect things.
> > > (image someone doing a bunch of ebuild installations for some kernel so
> > > they can tar up the bzImage and /lib/modules/${KV} for another box using
> > > portage.)
> > >
> > > So whenever possible, please grab all your info from /usr/src/linux
> > >
> > > Thanks for listening to my mini-rant. (:
> > >
> > > -pete
>
>