| 1 |
i'm looking to use catalyst to build binaries (grp?) that the local |
| 2 |
machines can use to install. i currently have a script which does the |
| 3 |
following: |
| 4 |
|
| 5 |
catalyst -s 2005.8 |
| 6 |
catalyst -f ./stage1.spec |
| 7 |
catalyst -f ./stage2.spec |
| 8 |
catalyst -f ./stage3.spec |
| 9 |
catalyst -f ./packagecd.spec.tmp |
| 10 |
|
| 11 |
after all is said and done, hopefully i have a |
| 12 |
builds/default/grp-i686-2005.8/cd2/All folder which contains binaries |
| 13 |
specified in the packagecd spec file. i merged the packagecd.spec.tmp |
| 14 |
with a client's machine's world file, so it may be rather long. next, |
| 15 |
i export the All folder and the clinets mount it on their |
| 16 |
/usr/portage/packages folder. |
| 17 |
|
| 18 |
i have a couple of questions with this method. |
| 19 |
|
| 20 |
1. i also get a folder structure of stage3-i686-2005.8/default/All or |
| 21 |
some such which contains some packages not found in the grp cd. is it |
| 22 |
ok to copy these packages over to the grp folder? i ask this one |
| 23 |
because my client machines are giving some x86 .vs. i686 errors with |
| 24 |
their gcc stuff after using the binaries to upgrade. thus some |
| 25 |
packages don't install from source for them. |
| 26 |
|
| 27 |
2. is there a more common method for building bin files to distribute |
| 28 |
to a bunch of internal users? |
| 29 |
|
| 30 |
3. how do i set the use flags for the binaries? i see the grp |
| 31 |
package can set use flags, is that enough? the machines have a pretty |
| 32 |
common use flag settings, but they seem to be slightly different than |
| 33 |
the default (dvd, etc). |
| 34 |
|
| 35 |
thanks! |
| 36 |
~mark |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-catalyst@g.o mailing list |
Archives