On Thu, Jan 08, 2004, Christopher Chan wrote:
> Will the OpenPKG tool work against the system default RPM database or
> does it always need to operate on its own database that it creates?
>
> If OpenPKG only works with its own database, does that mean that any
> dependencies during build I would need to re-install them in OpenPKG
> again even though my system already has them installed?
>
> A lot of package specs requires perl, python, gcc, glib2, etc....
Yes, OpenPKG is intentionally a fully self-contained sub-system on top
of your underlying operating system. One side-effect of this is that it
operates entirely on its own database and cannot take vendor packages
into account. So, yes, all dependencies have to be fulfilled within
OpenPKG.
On some platforms this might look strange (e.g. Linux where you usually
already have lots of tools available from the vendor), on others it
is essential (e.g. Solaris where you have mostly no additional stuff
available from the vendor or at least not in versions you would like
;-). But all this allows OpenPKG to be maximum independent of the
underlying operating system -- which is a key design goal of OpenPKG in
order to be a real unified cross-platform solution.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
