Wow, I am not quite sure how to respond Dennis, but let me start with a big 
'Thanks'.

I too would really like to see the community come together on this topic. If 
there are others out there who are interested in lending a hand and getting 
something out there for the community, please speak up!

RE: pkgsrc/make driven ports collections

Personally, I find the usage of darwinports to be the simplest to use and 
maintain. Makefile driven ports systems have a history of issues and are a bit 
clunky to use IMHO. This can also cause issues if the user is using sun's make 
versus gmake etc. (especially if /usr/sfw gets a home under /usr/gnu without 
'g' prefixing).

This may help a bit for those unfamiliar with dport semantics (assume we are 
installing irssi with ssl and ipv6):

darwinports:
    port install irssi +ssl +ipv6

vs. freebsd ports:
    cd /usr/ports/irc/irssi/ && make install clean WITH_SSL=yes WITH_IPV6=yes


Darwinports also generates package artifacts. It would be very nice to have the 
solaris port system do the same. This is very important, since it unifies *all* 
installed software under the solaris package management tools, which I know sun 
would be rather keen on.

I would also eventually like to see other opensol projects make use of the 
ports system rather than managing their own binary collections and bulid 
systems (Personally, I find building from .spec files onerous)

Thoughts?

Steve Stallion
 
 
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
[email protected]

Reply via email to