> Wow, I am not quite sure how to respond Dennis, but let me start with a big > 'Thanks'.
well, I have not done anything "real" for you yet. I do have a new server called phobos setup with snv_49 and the rest of the stack if it will help you get started. > > 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! > Sometimes you need to just jump in and start splashing and then others jump in the pool also. > 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? > Let me sit down to ThanksGiving Dinner up here in Canada and I will get back to you for sure ! Dennis _______________________________________________ opensolaris-help mailing list [email protected]
