From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: "gentoo-portage-dev@lists.gentoo.org"
<gentoo-portage-dev@lists.gentoo.org>
Subject: [gentoo-portage-dev] Portage questions
Date: Wed, 16 Sep 2015 13:13:40 +0000 [thread overview]
Message-ID: <1442409220.32234.28.camel@transmode.se> (raw)
1)
Is there a way to generate a snapshot of an installed portage VDB and then later
compare that snapshot against the current VDB and generate a list of
added/updated packages?
2)
Currently we generate a tar file with binary pkgs containing all updated pkgs,
unpack the tar file and emerge the binary pkgs with emerge --usepkgonly ...
into a new ROOT. This works but that misses any updates to the profile(both gentoo and our own).
To fix that we include a copy of both profiles in the tar file and copy our
updated profiles into the new ROOT profiles before merging. This feels a bit
clumsy and I wonder if there is a better way?
Jocke
next reply other threads:[~2015-09-16 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:13 Joakim Tjernlund [this message]
2015-09-20 7:26 ` [gentoo-portage-dev] Re: Portage questions Duncan
2015-09-20 16:47 ` [gentoo-portage-dev] " Zac Medico
2015-09-21 13:45 ` Joakim Tjernlund
2015-09-22 4:15 ` Zac Medico
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=1442409220.32234.28.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