1) /usr/sfw is moved into the ports collection (eventually of course), and we all live in a big happy world.
2) We build in alternate dependencies on /usr/sfw package in the event a companion package is not found on the system.
This really requires more explanation:
lets say that normally we depend on SUNWfoo to build a given package which just so happens to live in the companion. We can build the ports system in such a way that if the SUNWfoo dependency is not found on the system, we can build out an alternate package in the ports collection. Also, we could build in the option of upgrading the revision in place or support multiple revisions (again, more work, but would make users much happier in the long run).
Now here is the kicker. Ultimately I would like to see our ports package be used interchangeably throughout the entire system. Yes boys and girls, this means the possibility of installing to /usr or /usr/gnu or any other prefix we desire for a given package. Standards will most definitely need to be set, but imagine being able to actually use a hier that makes sense without require users to add yet more entries to their path. I would really like to see this done in such a way that once a port is built, it works in every way just as if the package came straight from sun. This most definitely needs sun endorsement, but in my mind, this would be one of the greatest strengths to obtaining third party software on solaris.
This does complicate things a bit, but imagine having the abillity to upgrade your version of JDS in place without having worrying about existing packages and revisions.
Admit it, its a nice thought ;)
Cheers!
Steve
On 10/9/06, Dennis Clarke <[EMAIL PROTECTED]> wrote:
> Dave,
>
> This may be ignorance on my part, but AFAIK, there are no TCL bindings to
> sun api's. In my experience, more developers (including myself) are more
> proficient in C than TCL. While TCL is in /usr/sfw, I would like to see the
> ports system available to any solaris user whether or not they have the
> software companion installed (read: binary distribution).
>
You know, that is one of the key ideas behind Blastwave. If you have a core
install of Solaris 8 ( or 9 or 10 or ... ) then you can install the binary
packages and not be dependant on some other thing that may or may not be in
/usr/sfw or /usr/local or /usr/foo.
The problem is that people have fits when they see that a package CSWfoo
drags in the national science museum history of dependencies *because* we
can NOT depend on any damn thing in /usr/sfw or whereever. Total
independance can mean that you drag a LOT of stuff around. Hence the vast
size of the Blastwave package dependency list.
Dennis
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
