1 |
On Sun, 2015-09-20 at 09:47 -0700, Zac Medico wrote: |
2 |
> On 09/16/2015 06:13 AM, Joakim Tjernlund wrote: |
3 |
> > 1) |
4 |
> > Is there a way to generate a snapshot of an installed portage VDB and then later |
5 |
> > compare that snapshot against the current VDB and generate a list of |
6 |
> > added/updated packages? |
7 |
> |
8 |
> This command will generate a flat file that is useful for comparisons |
9 |
> with diff -u: |
10 |
> |
11 |
> qlist -IvCURS | LC_ALL=C sort |
12 |
|
13 |
I was hoping for something akin to "emerge -pNDu world" but pointing emerge |
14 |
to another VDB. That would make it easier to see what has changed between then and now. |
15 |
|
16 |
> |
17 |
> > 2) |
18 |
> > Currently we generate a tar file with binary pkgs containing all updated pkgs, |
19 |
> > unpack the tar file and emerge the binary pkgs with emerge --usepkgonly ... |
20 |
> > into a new ROOT. This works but that misses any updates to the profile(both gentoo and our own). |
21 |
> > |
22 |
> > To fix that we include a copy of both profiles in the tar file and copy our |
23 |
> > updated profiles into the new ROOT profiles before merging. This feels a bit |
24 |
> > clumsy and I wonder if there is a better way? |
25 |
> > |
26 |
> > Jocke |
27 |
> > |
28 |
> |
29 |
> Like Duncan said, I feel like we're missing some context here. I wonder |
30 |
> why you use binary packages instead of a full system image, considering |
31 |
> that it's a "new ROOT." |
32 |
|
33 |
Every update to ROOT will be too big if one have use a full system image at every update. |
34 |
Instead we use BTRFS and create a snapshot of current / in a new BTRFS subvolume |
35 |
and install the updates into this snapshot, then just change default subvolume in BTRFS and |
36 |
reboot. |
37 |
To transfer profile changes before merging binary pkgs one have to copy these into |
38 |
the new ROOT. |
39 |
|
40 |
Jocke |