On Tue, Jun 03, 2008 at 03:37:31PM -0500, Nicolas Williams wrote:
> On Wed, Jun 04, 2008 at 02:01:37AM +0530, Venky wrote:
> > > We're talking about when the file dependency is resolved to a package
> > > dependency, which would at package publication time. See the rest of
> > > the thread.
> >
> > Err.. no. Dependencies need to be resolved at installation time.
> > It does not matter if they are file-based or package-based.
>
> Read the rest of the thread. We're talking about expressing some
> dependencies in a way that gets translated into normal dependencies on
> packages at publication time. Of course dependencies must be handled as
> usual at pkg install time.
I must be explaining myself very badly. Let me try again. I see no
reason why there needs to be a translation of file-based
dependencies into normal dependencies *at publication time*. (If
you can come up with a reason, please let me know.) The server, in
fact, should not even care about the specified dependency. It is up
to the pkg client to resolve it.
A file-based dependency is similar to a FMRI-based one. The only
difference is that the client will figure out (at installation time)
the FMRI of the package that satisfies this dependency. If there
are multiple alternatives, it displays the list to the user and
aborts. The user would need to pull one of them in explicitly
before trying to install this package again.
There is no need for a separate mode of operation, prompting the
user for choices, etc. IMO, this should just be an extension of the
way pkg works right now.
Venky.
PS: If you read the rest of this thread, you will find one of the
examples I mentioned earlier about "mutt" depending on
"/usr/lib/sendmail". That is the example I was using to make my
point that resolving dependencies at publication time does not
make sense.
--
One hundred thousand lemmings can't be wrong.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
