| 1 |
Apparently, though unproven, at 10:55 on Thursday 23 September 2010, Helmut |
| 2 |
Jarausch did opine thusly: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> when portage installs a package, it first installs it into some "shadow |
| 7 |
> root". Then it records all files installed before it moves the files to |
| 8 |
> the "real root". |
| 9 |
> |
| 10 |
> I have to do some installations on SUSE systems (which are not |
| 11 |
> administered by me) and I'd like to imitate that procedure there. |
| 12 |
> |
| 13 |
> Can anybody tell me if it's not too complicated and if yes, how to |
| 14 |
> achieve this (on a foreign system like SUSE). |
| 15 |
> |
| 16 |
> Many thanks for your help, |
| 17 |
> Helmut. |
| 18 |
|
| 19 |
|
| 20 |
1. Remove all traces of yast and it's bastard brethren from the SuSE box. |
| 21 |
2. Have three qualified sysadmins double check that you have indeed removed |
| 22 |
every last trace of it. |
| 23 |
3. PREFIX=/some/stage/dir/ |
| 24 |
4. ./configure && make && make install |
| 25 |
5. find /some/stage/dir/ > some_file |
| 26 |
6. move everything in stage dir to real dir |
| 27 |
|
| 28 |
Why remove yast? |
| 29 |
Because it's a sneaky P.O.S. and goes to extraordinary lengths to nuke all |
| 30 |
your hard work done without it. |
| 31 |
|
| 32 |
And how you deal with file collisions is up to you. Yast really won't like you |
| 33 |
if you overwrite some config file with your own testing version. |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
alan dot mckinnon at gmail dot com |
Archives