On Tue, 2005-03-29 at 15:05 -0700, Grant Likely wrote: <snip> > > I think I've got my head better wrapped around gentoo-embedded, but I > have some new questions I would like to ask. > > As it stands right now, it seems that /etc/make.conf and the > make.profile symlinks need to be explicitly modified to support cross > compiling. (portage_const.py appears to hardcode both /etc/make.conf > and /etc/make.profile locations). This means that you need to manully > switch between configured for native emerges and emerges for the cross > target. Is this true? If so, is anybody working on decoupling emerge > so that it can use a totally seperate set of configuration files as > specified by the environment or command line?
Yes, I've got a bug open for this. https://bugs.gentoo.org/show_bug.cgi?id=73350 It's going to be a while though. For the most part, I just use environment variables on the command line to override everything. (I have some bashrc aliases setup to help out) > > It does not appear that there is any support for running emerge as > non-root. Are there any plans to do so? I think there is a bug about this too, but you have to find it on your own. At the very least, you have to be in the portage group. > > The reason I ask these questions is that for my environment I want to > be able to build a rootfs with limited root access. Ideally I would > like to be able to run everything as a user and use fakeroot w/ > mkfs.jffs2 to build the target image. What changes would I need to > look into to get portage to support this model? Is this even > feasable/desireable? desireable: yes, feasible: with time > > Thanks, > g. > > -- > [email protected] mailing list > -- FOR SALE: Epia M10000 with 256M ram 125 Hauppauge PVR 350 150 For the full list see: http://www.brianandsara.net/temp/forsale.php -- [email protected] mailing list
