Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-kernel
Lists: gentoo-kernel: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-kernel <gentoo-kernel@g.o>
From: Daniel Gryniewicz <dang@g.o>
Subject: Installation location in kernel-2.eclass
Date: Sun, 23 Jul 2006 16:44:22 -0400
Hey, all.

UML is a bit of a unique animal, in the kernel world.  You install it on
a box, and run it on that box, but it's not the kernel for that box.
For this reason, I think it would be useful to be able to install UML
into a different location than /usr/src.  I, for example, always do my
UML work in /home/os/uml, and would like to install it there.  I could
symlink, but that would break my bind mounts, and cause other problems,
so I always end up copying it.

Unfortunately, kernel-2.eclass hardcodes the install directory to
be /usr/src.  To get around this problem, I propose that a variable be
added to kernel-2.eclass (I named it K_TARGETDIR) that can be set in an
ebuild to install to somewhere else than /usr/src.  It should default,
of course, to /usr/src.  In usermode-sources, I'd use this as follows:


This would allow the user to specify USERMODE_TARGET_DIR in either
make.conf or on the command line, and install usermode-sources in that
directory, rather than /usr/src.

What do people think about this idea?  Is there a better way to do this?

k_targetdir.patch (Text Data)
signature.asc (This is a digitally signed message part)
Lists: gentoo-kernel: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[ANNOUNCE] genpatches-2.6.17-5 release
Next by thread:
[ANNOUNCE] genpatches-2.6.17-6 release
Previous by date:
[ANNOUNCE] genpatches-2.6.17-5 release
Next by date:
[ANNOUNCE] genpatches-2.6.17-6 release

Updated Jun 17, 2009

Summary: Archive of the gentoo-kernel mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.