On 13/11/19 19:07, Zac Medico wrote: > On 11/8/19 9:09 AM, Joakim Tjernlund wrote: >> On Fri, 2019-11-08 at 01:57 +0100, Joakim Tjernlund wrote: >>> I am looking for a way to seed emerge with an older pkg db so emerge can >>> calculate >>> which packages needs to be rebuild/upgraded in order to get to the same >>> state as the system pkg db, >>> Is that possible? >>> >>> Also, is there some tool that allows med to copy just files needed for a >>> profile? >>> Something like "cp" /etc/portage/make.profile /my/destination >>> >> portage-utils has variables Q_VDB and Q_EDB which allows qmerge to use >> different VDBs/EDBs >> Does portage have something similar? > No, nothing like either of those things. > > However, if you want to operate on an old system then the usual > recommendation is to unpack a stage3 and bind mount the old system root > into the stage3 so that you can chroot into the stage3 and run something > like this: > > emerge --root /mnt/old-system portage In the interests of clarity, what does this achieve, and what would the next couple of steps look like? (actual commands not necessary, pseudo-code WFM)
signature.asc
Description: OpenPGP digital signature
