1 |
On 14:27 Tue 11 Oct , Eric Edgar wrote: |
2 |
> On 07:36 Tue 11 Oct , Mark Lybarger wrote: |
3 |
> > i'm looking to use catalyst to build binaries (grp?) that the local |
4 |
> > machines can use to install. i currently have a script which does the |
5 |
> > following: |
6 |
> > |
7 |
> > catalyst -s 2005.8 |
8 |
> > catalyst -f ./stage1.spec |
9 |
> > catalyst -f ./stage2.spec |
10 |
> > catalyst -f ./stage3.spec |
11 |
> > catalyst -f ./packagecd.spec.tmp |
12 |
> > |
13 |
> > after all is said and done, hopefully i have a |
14 |
> > builds/default/grp-i686-2005.8/cd2/All folder which contains binaries |
15 |
> > specified in the packagecd spec file. i merged the packagecd.spec.tmp |
16 |
> > with a client's machine's world file, so it may be rather long. next, |
17 |
> > i export the All folder and the clinets mount it on their |
18 |
> > /usr/portage/packages folder. |
19 |
> > |
20 |
> > i have a couple of questions with this method. |
21 |
> > |
22 |
> > 1. i also get a folder structure of stage3-i686-2005.8/default/All or |
23 |
> > some such which contains some packages not found in the grp cd. is it |
24 |
> > ok to copy these packages over to the grp folder? i ask this one |
25 |
> > because my client machines are giving some x86 .vs. i686 errors with |
26 |
> > their gcc stuff after using the binaries to upgrade. thus some |
27 |
> > packages don't install from source for them. |
28 |
> I believe its ok to do that. grp is basically just an extension of |
29 |
> stage3so it shouldnt be an issue. I will have to talk with wolf31o2 but |
30 |
> that might be a feature to add to catalyst2. IE have grp and stage3 put |
31 |
> the pkgs in the same destination folder. |
32 |
Better yet would be to put the missing system packages in the spec file |
33 |
so that they are rebuilt with the appropriate use flags if necessary and |
34 |
that would automatically build the new packages needed for the other |
35 |
systems |
36 |
> |
37 |
> > |
38 |
> > 2. is there a more common method for building bin files to distribute |
39 |
> > to a bunch of internal users? |
40 |
> Not that I know of. Catalyst is pretty much one of the best tools for |
41 |
> doing this. You may want to look at the tinderbox target though as that |
42 |
> builds each package individually and you can find out specific ones that |
43 |
> fail. Its something to look at. |
44 |
> > |
45 |
> > 3. how do i set the use flags for the binaries? i see the grp |
46 |
> > package can set use flags, is that enough? the machines have a pretty |
47 |
> > common use flag settings, but they seem to be slightly different than |
48 |
> > the default (dvd, etc). |
49 |
> That is enough. With catalyst2 you will be able to setup the |
50 |
> /etc/portage structure as well and have per package use flags setup. |
51 |
> |
52 |
> > |
53 |
> > thanks! |
54 |
> > ~mark |
55 |
> > |
56 |
> > -- |
57 |
> > gentoo-catalyst@g.o mailing list |
58 |
> > |
59 |
> > |