At Thu, 28 Jan 2010 07:16:45 +0000, David Holland
<dholland-pkgtech%netbsd.org@localhost> wrote:
Subject: Re: Pkgsrc on systems with existing package systems
>
> On Mon, Jan 25, 2010 at 08:40:23PM -0500, Greg A. Woods wrote:
> > Fink uses the Debian dpkg(8) package manager under the hood, and it
> > creates "virtual" packages to represent underlying OS X components and
> > packages (including I think at the OS X pkgutil(1) level).
> >
> > Perhaps pkgsrc could do something similar to integrated with a
> > platform's existing package system?
> >
> > This might help bootstrap easier on some platforms, but of course it
> > might also cause conflicts with the way one might wish to install a
> > different version of some package vs. the one already provided.
>
> The builtin logic does essentially this, although it doesn't generate
> shadow packages. That has both positive and negative results. But the
> conflict issue can be handled by explicitly setting USE_BUILTIN.*.
I hadn't thought of it that way, but yeah, I see what you mean....
Having seen fink in action now though I think there are some possible
advantages to making explicit "shadow"/"virtual" packages to represent
components on the host system that may have been installed from the base
OS or from some other source.
I'm not 100% sure of it's internals and workings, but I think fink may
be using these shadow packages as dependencies for both runtime and
build-time (or both) for its own packages.
Then shadow packages (and appropriate buildlink modules -- perhaps
buildlink modules should then be installed as part of the binary
package?) could be created for anything that might already be available
on a given system, be it installed from the base OS, or some other
packaging tool, etc. Of course this is also potentially one very fine
and very long piece of rope to play with too.
--
Greg A. Woods
Planix, Inc.
<woods%planix.com@localhost> +1 416 218 0099 http://www.planix.com/
Attachment:
pgpoXCfeTvUUk.pgp
Description: PGP signature