Hi Bill & Rest.
* Bill Campbell <[EMAIL PROTECTED]> [060325 00:44]:
> On Fri, Mar 24, 2006, bak wrote:
*snip*
> Our nightly mirror update script first rsync's the directories
> from the OpenPKG.org site to the appropriate directories here,
> then hard links new *.src.rpm packages into the private directory,
> exluding ones that we've modified locally.
This is basically the same thing I currently do on my 'build'
server. But instead of hardlinking the files from the rsync mirror
directory, I have a 00INDEX.rdf file that simply includes the
different bits stored below /export/openpkg/... That works well for me
since I haven't changed any openpkg packages but instead forked them
and gave them new names.
*snip*
> We have one user account (the %{l_musr} account) set up with
> their ~/.openpkg/build file with the options set for each
> package. The ``openpkg build'' command uses this file to
> generate the appropriate ``--define'' options to build each
> package.
Didn't know I could set with_XXX options in ~/.openpkg/build. Good to
know (maby I should read the man pages more carefully :)
> This doesn't answer the question on how one would use the
> ``openpkg build'' command to update a system from a binary
> repository which is something that would be very useful when
> maintaining ``appliance'' type servers that have identical
> hardware.
Exactly. I have a number of identical servers hosting several
applications for clients. My current approach to installing / updating
packages is rsyncing the binary packages form the build server and an
editied version of the 'openpkg build' script that installs / updates
only the Preq packages. I quess when 'openpkg install' is implemented
it would do just what I want.
-- Olaf
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
