public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: "gentoo-portage-dev@lists.gentoo.org"
	<gentoo-portage-dev@lists.gentoo.org>
Subject: Re: [gentoo-portage-dev] @sets and @profile does not work when ROOT=PORTAGE_CONFIGROOT=/my/new/root
Date: Thu, 22 Oct 2015 07:05:20 +0000	[thread overview]
Message-ID: <1445497519.31293.50.camel@transmode.se> (raw)
In-Reply-To: <562867A7.3010108@gentoo.org>

On Wed, 2015-10-21 at 21:35 -0700, Zac Medico wrote:
> On 10/21/2015 09:47 AM, Joakim Tjernlund wrote:
> > I have enabled @sets and @profile in my own profile and if I add
> > some pkg to either my new set or @profile in ROOT=PORTAGE_CONFIGROOT=/
> > then emerge -aNDuv world notices this and pulls in the new pkg.
> > 
> > Then I clone / to  /my/new/root and add a pkg @profile or my set 
> > ROOT=/my/new/root PORTAGE_CONFIGROOT=/my/new/root emerge -aNDuv world nothing happens.
> > 
> > This feels like @profile and @sets looks in ROOT=PORTAGE_CONFIGROOT=/
> > instead of ROOT=PORTAGE_CONFIGROOT=/my/new/root
> > 
> > if I in my new ROOT(/my/new/root) add pkg to the @system set it works.
> > 
> > Does this make sense to you?
> > 
> >   Jocke
> > 
> 
> Are there any special details about your set configuration that we might
> need to consider? The following strace command seems to show that
> load_emerge_config uses the correct world file when the ROOT variable is
> set:

I don't use world_sets, I have in my profile(/my/new/root/usr/local/portage/tmv3-target-overlay):
# > cat sets.conf 
[CUSFPv3 sets]
class = portage.sets.files.StaticFileSet
multiset = true
directory = ${repository:tmv3-target-overlay}/sets/

[world]
class = portage.sets.base.DummyPackageSet
packages =  @cusfpv3 @profile @selected @system

and in sets/:
# > cat sets/cusfpv3
net-ftp/ftp
net-ftp/tftp-hpa
net-ftp/vsftpd
....

and now it hits me, this line:
 directory = ${repository:tmv3-target-overlay}/sets/
does it always refer too ROOT=/ ?

> 
> $ ROOT=/mnt/gentoo strace python -c 'from _emerge.actions import
> load_emerge_config;
> load_emerge_config().target_config.setconfig.getSetAtoms("world")' 2>&1
> > grep world
> stat("/usr/lib64/python3.4/site-packages/_emerge/create_world_atom.py",
> {st_mode=S_IFREG|0644, st_size=4414, ...}) = 0
> stat("/usr/lib64/python3.4/site-packages/_emerge/create_world_atom.py",
> {st_mode=S_IFREG|0644, st_size=4414, ...}) = 0
> open("/usr/lib64/python3.4/site-packages/_emerge/__pycache__/create_world_atom.cpython-34.pyc",
> O_RDONLY|O_CLOEXEC) = 4
> read(4, "# required by @world (argument)\n"..., 8192) = 8192
> read(4, "# required by @world (argument)\n"..., 8192) = 8192
> stat("/mnt/gentoo/var/lib/portage/world", {st_mode=S_IFREG|0644,
> st_size=14364, ...}) = 0
> stat("/mnt/gentoo/var/lib/portage/world", {st_mode=S_IFREG|0644,
> st_size=14364, ...}) = 0
> open("/mnt/gentoo/var/lib/portage/world", O_RDONLY|O_CLOEXEC) = 4
> stat("/mnt/gentoo/var/lib/portage/world_sets", {st_mode=S_IFREG|0644,
> st_size=0, ...}) = 0
> stat("/mnt/gentoo/var/lib/portage/world_sets", {st_mode=S_IFREG|0644,
> st_size=0, ...}) = 0
> open("/mnt/gentoo/var/lib/portage/world_sets", O_RDONLY|O_CLOEXEC) = 4
> stat("/mnt/gentoo/var/lib/portage/world", {st_mode=S_IFREG|0644,
> st_size=14364, ...}) = 0
> stat("/mnt/gentoo/var/lib/portage/world", {st_mode=S_IFREG|0644,
> st_size=14364, ...}) = 0
> open("/mnt/gentoo/var/lib/portage/world", O_RDONLY|O_CLOEXEC) = 4
> stat("/mnt/gentoo/var/lib/portage/world_sets", {st_mode=S_IFREG|0644,
> st_size=0, ...}) = 0
> stat("/mnt/gentoo/var/lib/portage/world_sets", {st_mode=S_IFREG|0644,
> st_size=0, ...}) = 0
> open("/mnt/gentoo/var/lib/portage/world_sets", O_RDONLY|O_CLOEXEC) = 4


  reply	other threads:[~2015-10-22  7:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 16:47 [gentoo-portage-dev] @sets and @profile does not work when ROOT=PORTAGE_CONFIGROOT=/my/new/root Joakim Tjernlund
2015-10-22  4:35 ` Zac Medico
2015-10-22  7:05   ` Joakim Tjernlund [this message]
2015-10-22 15:54     ` Zac Medico
2015-10-22 18:29       ` Joakim Tjernlund
2015-10-22 18:54         ` Zac Medico
2015-10-22 19:16           ` Joakim Tjernlund
2015-10-22 19:25             ` Zac Medico
2015-10-22 20:54               ` Joakim Tjernlund
2015-10-22 21:08                 ` Zac Medico
2015-10-23  5:03           ` [gentoo-portage-dev] " Duncan
2015-10-23  9:21           ` [gentoo-portage-dev] " Joakim Tjernlund
2015-10-24 20:49             ` Zac Medico
2015-10-23  1:36         ` [gentoo-portage-dev] [PATCH] RepoConfigLoader: allow subsitution of variables like ROOT in repos.conf Zac Medico
2015-10-28 13:28           ` Brian Dolbec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1445497519.31293.50.camel@transmode.se \
    --to=joakim.tjernlund@transmode.se \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox