Hi,

I'm fairly new to OpenPKG and perhaps my question has already been
answered or is moot by some feature I don't know about.  

We are using OpenPKG packages "out of the box" but we also maintain
a small local repository with some packages that we built ourselves 
or have customised using the stock OpenPKG packages as the base.  For
example, we need shared libs built out of some packages that per 
default only build static libs, or other things that cannot be 
easily specified during package build time.

I would like to start using the "openpkg build" command using both 
the OpenPKG CURRENT repository and our own customised one. I've 
made an index file that looks roughly like this:

<Repository rdf:resource="mycompany">
  <Repository rdf:resource="mycompany" href="other/00INDEX.rdf"/>
  <Repository rdf:resource="OpenPKG-CURRENT/Source/" 
href="ftp://ftp.openpkg.org/current/SRC/00INDEX.rdf.bz2"/>
</Repository>

A "openpkg build -r <repository dir>" works fine with this, it 
collects the package indexes from both locations and seems to merge
them as expected.

My problem is the following.  Suppose we want to install the latest
of mysql but only the customised package.  If the latest version in
the OpenPKG CURRENT repository is the same or newer than the one we
have in our custom repository, the OpenPKG CURRENT will be used when
we do a "openpkg build -r <repository dir> mysql".  This would be 
undesirable as we want our own version to be preffered, even if that's
running behind a few releases.

Is it somehow possible to set a preference for a certain repository 
so that in case the package is present in both repositories one of
those will be preferred regardless of the version or release (or 
both)?

Thanks,

-- 
Paul Vlaar             |  APNIC Secretariat
Systems Administrator  |  http://www.apnic.net/
email: [EMAIL PROTECTED]   |  Level 1, 33 Park Road,
phone: +61 7 3858 3100 |  PO Box 2131, Milton 
  fax: +61 7 3858 3199 |  QLD 4064, Australia.
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [EMAIL PROTECTED]

Reply via email to