i'm looking to use catalyst to build binaries (grp?) that the local
machines can use to install.  i currently have a script which does the
following:

catalyst -s 2005.8
catalyst -f ./stage1.spec
catalyst -f ./stage2.spec
catalyst -f ./stage3.spec
catalyst -f ./packagecd.spec.tmp

after all is said and done, hopefully i have a
builds/default/grp-i686-2005.8/cd2/All folder which contains binaries
specified in the packagecd spec file.  i merged the packagecd.spec.tmp
with a client's machine's world file, so it may be rather long. next,
i export the All folder and the clinets mount it on their
/usr/portage/packages folder.

i have a couple of questions with this method.

1. i also get a folder structure of stage3-i686-2005.8/default/All or
some such which contains some packages not found in the grp cd.  is it
ok to copy these packages over to the grp folder?  i ask this one
because my client machines are giving some x86 .vs. i686 errors with
their gcc stuff after using the binaries to upgrade.  thus some
packages don't install from source for them.

2. is there a more common method for building bin files to distribute
to a bunch of internal users?

3. how do i set the use flags for the binaries?   i see the grp
package can set use flags, is that enough?  the machines have a pretty
common use flag settings, but they seem to be slightly different than
the default (dvd, etc).

thanks!
~mark

-- 
gentoo-catalyst@g.o mailing list