Passing PORTAGE_CONFIGDIR and ROOT at the same time allows
I haven't found anything (even inside make.conf manpages or the example) about the PORTAGE_CONFIGDIR variable. I suppose that it would change the default locations of the make.conf (and friends) location. This way, it would be possible to compile a 586 target inside a 686 machine, using the PORTAGE_CONFIGDIR and ROOT variables, right? Thanks for the help! 2007/7/12, Christopher Friedt <[EMAIL PROTECTED]>:
I think the 'tinygentoo' howto is quite useful for what you're talking about. Passing PORTAGE_CONFIGDIR and ROOT at the same time allows you to build a very minimal system. I usually just symlink /usr/portage to /tinygentoo/usr/portage, but you could just as easily mount -o bind it. I guess what's assumed in this case is that you're compiling for the same arch. Which arch are you using? Is there a qemu-system that is capable of running natively compiled binaries for your arch? I use busybox / (uclibc or glibc, without many of the locales) and have made several very small root filesystems, but mainly for ARM. ~/Chris Marcelo Coelho wrote: > Hi! > > > I'm trying to create a minimal system and using the ROOT var to set > the location where I want the packages to be installed. > > The problems arise when I tried to choose a cron daemon: I would have > to install 39 packages, including portage. > > How can I trim the package set that would be emerged together with the > cron daemon or other packages? > > When emerging with the ROOT var (eg.: /var/system), the make.conf file > that is used is the one that is located at that location (eg.: > /var/system/etc/make.conf) ? > > What normally are the packages that you guys use as minimal system? > > > Thanks for the help! -- [EMAIL PROTECTED] mailing list
-- [EMAIL PROTECTED] mailing list
