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