On Sat, 2015-05-09 at 10:49 -0700, Zac Medico wrote: > On 05/09/2015 10:08 AM, Joakim Tjernlund wrote: > > On Sat, 2015-05-09 at 09:36 -0700, Zac Medico wrote: > > > On 05/09/2015 06:47 AM, Joakim Tjernlund wrote: > > > > On Fri, 2015-05-08 at 11:32 -0700, Zac Medico wrote: > > > > > On 05/07/2015 11:43 PM, Joakim Tjernlund wrote: > > > > > > On Thu, 2015-05-07 at 14:09 -0700, Zac Medico wrote: > > > > > > > On 05/07/2015 03:51 AM, Joakim Tjernlund wrote: > > > > > > > > On Wed, 2015-05-06 at 22:45 +0000, Joakim Tjernlund wrote: > > > > > > > > > On Wed, 2015-05-06 at 15:16 -0700, Zac Medico wrote: > > > > > > > > > > On 05/06/15 14:57, Joakim Tjernlund wrote: > > > > > > > > > > > On Wed, 2015-05-06 at 14:36 -0700, Zac Medico wrote: > > > > > > > > > > > > On 05/06/15 14:30, Joakim Tjernlund wrote: > > > > > > > > > > > > > On Wed, 2015-05-06 at 13:30 -0700, Zac Medico wrote: > > > > > > > > > > > > > > On 05/06/15 13:22, Joakim Tjernlund wrote: > > > > > > > > > > > > > > > On Wed, 2015-05-06 at 12:54 -0700, Zac Medico > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > The idea is that you have separate repositories > > > > > > > > > > > > > > configured for each > > > > > > > > > > > > > > ROOT. If it's satisfying a build-time DEPEND that > > > > > > > > > > > > > > will be installed into > > > > > > > > > > > > > > ROOT=/, then it's supposed to use the repositories > > > > > > > > > > > > > > configured for ROOT=/. > > > > > > > > > > > > > > > > > > > > > > > > > > I see, but in my case I only install into my sysroot > > > > > > > > > > > > > so I don't want this behaviour. > > > > > > > > > > > > > > > > > > > > > > > > So, why don't you use the --root-deps option? > > > > > > > > > > > > > > > > > > > > > > Just did(and --root-deps=rdeps too) and it didn't work, > > > > > > > > > > > still wants to use > > > > > > > > > > > my newer hosts pkgs. :( > > > > > > > > > > > > > > > > > > > > It shouldn't do that. It sounds like maybe the [gentoo] > > > > > > > > > > config > > > > > > > > > > from/usr/share/portage/config/repos.conf is the source of > > > > > > > > > > your problems, > > > > > > > > > > since you $PORTAGE_CONFIGROOT config will always inherit > > > > > > > > > > that. Would > > > > > > > > > > that be consistent with your observations? > > > > > > > > > > > > > > > > > > Moving that file out of the way changed things, now I got I > > > > > > > > > profile error: > > > > > > > > > !!! Unable to parse profile: '/etc/portage/make.profile' > > > > > > > > > !!! ParseError: Parent 'gentoo:default/linux/amd64/13.0' not > > > > > > > > > found: > > > > > > > > > '/var/lib/layman/transmode/profiles/gentoo64-server/parent' > > > > > > > > > !!! Your current profile is invalid. If you have just changed > > > > > > > > > your profile > > > > > > > > > !!! configuration, you should revert back to the previous > > > > > > > > > configuration. > > > > > > > > > !!! Allowed actions are limited to --help, --info, --search, > > > > > > > > > --sync, and > > > > > > > > > !!! --version. > > > > > > > > > > > > > > > > > > Which I think is a problem in my cross env. > > > > > > > > > > > > > > > > No, this is not it. Portage just bails when reading the host > > > > > > > > profile which it should not. > > > > > > > > > > > > > > > > Note: defining > > > > > > > > PORTAGE_REPOSITORIES=/my/own/repos.conf > > > > > > > > gives the same error. > > > > > > > > > > > > > > > > > > > > > > According to the error message, your transmode profile inherits a > > > > > > > gentoo > > > > > > > profile, so you need the gentoo repository (at least the relevant > > > > > > > profile). > > > > > > > > > > > > I have a my own profile in PORTAGE_CONFIGROOT which does not > > > > > > reference the host /etc/portage/make.profile at all so I think > > > > > > portage is using the wrong profile. > > > > > > > > > > When using ROOT=/foo, it always instantiates 2 profiles, and it uses > > > > > one > > > > > profile for ROOT=/foo and the other profile for ROOT=/. > > > > > > > > This makes sense when just using ROOT, not when cross compiling. > > > > If I cross build (or use PORTAGE_REPOSITORIES ?) I don't think it makes > > > > sense to add the hosts profile as it has little to nothing to > > > > do with my cross target. > > > > How would a cross target use the hosts profile sensibly? > > > > > > The host profile is only used for packages installed to ROOT=/ in order > > > to satisfy DEPEND. If you use the emerge --root-deps then the host > > > profile is used for absolutely nothing (although it is still > > > instantiated). > > > > I see, it would be nice if it wasn't instantiated when not needed so > > one could avoid the error I have seen. > > > > > > > > > > > > > > > > Futhermore, it does not understand the host profile, probably > > > > > > because my own PORTAGE_CONFIGROOT don't have profile-formats = > > > > > > portage-2 > > > > > > > > > > You're saying this beciase of the above ParseError? I think maybe what > > > > > you want to do keep the default /usr/share/portage/config/repos.conf > > > > > and > > > > > mask */*::gentoo in $PORTAGE_CONFIGROOT/etc/portage/package.mask. > > > > > > > > That is what I am doing now, but that still includes the hosts profile > > > > I think ? > > > > > > It will only be used for packages installed to ROOT=/ in order to > > > satisfy DEPEND, as I have mentioned above. > > > > OK, you always read the host profile in case you need it. > > May I suggest you avoid touching the host profile when it not used(cross > > complies)? > > I suppose we could lazily instantiate the config for ROOT=/ at the point > where a a DEPEND needs to be satisfied (or HDEPEND for EAPI 5-hdepend). > See this bug: > > https://bugs.gentoo.org/show_bug.cgi?id=324179
Right, seen that bug before :) However, there may be a another bug in here. Portage is complaining over not being able to load the hosts profile as the hosts is using "profile-formats = portage-2" and my CONFIGROOT is not. I don't think my CONFIGROOT should be forced to use "profile-formats = portage-2" just because the host is? Jocke
