| 1 |
On 29/03/2004, at 9:21 PM, Paul de Vrieze wrote: |
| 2 |
> Well help2man is a compile-time dependency. At installation time the |
| 3 |
> man |
| 4 |
> pages have allready been generated so this dependency is not needed. |
| 5 |
|
| 6 |
This is the exact sequence that generates the problem: |
| 7 |
|
| 8 |
mkdir build |
| 9 |
cd build |
| 10 |
tar jxpf ../stage2-i686-20040218.tar.bz2 # from 2004.0 |
| 11 |
|
| 12 |
# Update the stage 2 build to an up-to-date stage 3 |
| 13 |
chroot . sh -c " |
| 14 |
export CONFIG_PROTECT='-*' |
| 15 |
emerge sync |
| 16 |
emerge -gb system # doesn't like update at this stage |
| 17 |
emerge -bu --deep world # should have 'g' but emerge bug" |
| 18 |
|
| 19 |
The first time through, the pre-compiled packages server is empty. I |
| 20 |
then copy the built packages to the server, wipe the test build, and |
| 21 |
start it again from scratch. This is why it's a bit confusing to see |
| 22 |
any difference at all. |
| 23 |
|
| 24 |
I'd like to be able to put the 'g' in the last command, but it |
| 25 |
generates different results. |
| 26 |
|
| 27 |
Yes, the above is essentially repeating what catalyst does, but the |
| 28 |
above script is going to continue into customising for internal |
| 29 |
deployment (eg, where catalyst leaves off). |
| 30 |
|
| 31 |
The avenue I'm investigating is a combination of repeatable build |
| 32 |
scripts and radmind for administrating machines, then I'm intending to |
| 33 |
write my own radmind/rsync tool to fill in the gaps. |
| 34 |
|
| 35 |
All interesting stuff. :) |
| 36 |
|
| 37 |
-- |
| 38 |
steve@×××××××××××××××.au |
| 39 |
|
| 40 |
CRICOS Provider Number 00123M |
| 41 |
------------------------------------------------ |
| 42 |
This email message is intended only for the addressee(s) |
| 43 |
and contains information that may be confidential and/or |
| 44 |
copyright. If you are not the intended recipient please |
| 45 |
notify the sender by reply email and immediately delete |
| 46 |
this email. Use, disclosure or reproduction of this email |
| 47 |
by anyone other than the intended recipient(s) is strictly |
| 48 |
prohibited. No representation is made that this email or |
| 49 |
any attachments are free of viruses. Virus scanning is |
| 50 |
recommended and is the responsibility of the recipient. |
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-dev@g.o mailing list |
Archives