It seems to be a question of binding time. Doing the mapping at package
publishing time will produce a different result than mapping at package
install time with multiple repositories in play.
Tom
[EMAIL PROTECTED] wrote:
Why would you need this functionality if we implement a way to map files to
pkg dependencies?
-j
On Wed, Jun 04, 2008 at 04:11:36AM +0530, Venky wrote:
(Splitting the thread.)
You're talking about a mechanism that explicitly encodes file
dependencies in the manifest. This is orthogoal to the current
discussion.
Okay. So, would it make sense to encode file dependencies in the
manifest? Based on this conversation, I'm assuming the answer is
going to be no, but it would be good to know the reasons (or a link
to the thread if this has been hashed out before).
As demonstrated, this behaviour is easy enough to simulate using the
existing tools and some extra meta-data. What would be the problem
with adding explicit support for it?
Venky.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
begin:vcard
fn:Tom Mueller
n:Mueller;Tom
org:Sun Microsystems, Inc.;SWI Install/Update Software
adr:;;21915 Hillandale Dr;Elkhorn;NE;68022;USA
email;internet:[EMAIL PROTECTED]
title:Senior Staff Engineer
tel;work:877-250-4011
tel;fax:877-250-4011
tel;home:402-916-9943
x-mozilla-html:TRUE
version:2.1
end:vcard
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
