[email protected] wrote:
> However, this also allows you to
> solve the case where your application needs perl 5.6, and another
> application needs perl 5.8, but you need intermediate versions of these
> as well as the latest. If you tell verexec to launch /usr/bin/perl5.6
> and /usr/bin/perl5.8, it'll find 5.6.2 and 5.8.9 if they are installed.
> If you want to leave 5.8.4 installed for testing you can do that, but
> any scripts that specify 5.8 without any further refinement get 5.8.9
> (latest).
Your scenario seems like it reduces to the core functionality, if you
think of perl, perl5.6 and perl5.8 as separate programs resolved
independently.
A simple install-time-only scheme like I suggested would handle this
case easily.
perl 5.6.2
action verexec /usr/bin/perl5.6
action verexec /usr/bin/perl
perl 5.8.4
action verexec /usr/bin/perl5.8
action verexec /usr/bin/perl
perl 5.8.9
action verexec /usr/bin/perl5.8
action verexec /usr/bin/perl
/usr/bin/perl5.6 would point to the newest binary from
the set of packages that names /usr/bin/perl5.6 with a
verexec action.
Similarly for perl and perl5.8 symlinks.
--chris
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
