Steve I like to invite you take a look at TWW's opensource package offering. I believe it is a superset of Solaris Companion packages and it is GNU opensourced.
ftp://support.thewrittenword.com/dists/7.1/src/ All of your three conerns has been addressed by TWW's Hyper Package Management System. it also provide a softare build sytem, package build system. we we need to do is recompile it to opensolaris' installation path that we agree upon. for those who can't goes with agreed installation path, fine, recompile the package source to have your own installation to meet your need. /opt/csw,/opt/sfw or /opt/twwfsw or /usr/local ;). I used to use your packages and read your notes on compiling pkgadd package and I found the process of software build is not fully digitalized, others can't repeat easily without pains. TWW's software build package source is well designed so others can easily build tar ball and install binary easily by command "sb zip-2.3/sb-db.xml;sb -i zip-2.3/sb-db.xml'. and creating a package for solaris is also just one command away by "pb zip-2.3/sb-db.xml'. please see http://en.wikibooks.org/wiki/CPAM_with_TWW/User_Guide to get started. > 1. What are our packaging goals? > 2. What systems are available and what are the pros > and cons of each? I think this wiki http://en.wikibooks.org/wiki/OpenSolaris/Reference_Manual share the similar goal of "Solaris Companion community developement". I really don't have bandwidth to compare all. Can we do this by teamwork on wiki to compare pros/cons of major PMS ? tj > Glynn - > > It may be a little early to create a community, but > not too early to > start defining the problems we need to solve and what > a community > might do. What I would like to see immediately here > is a good summary > of > > 1. What are our packaging goals? > 2. What systems are available and what are the pros > and cons of each? > Some of my concerns are > > 1. having a system that is relatively easy to learn > so that developers > will not be put off by it. Some systems may be very > powerful, but > hard > to learn. I favor simplicity whenever possible so > that new users will > not be too confused. > > 2. for creation of a package, having a system that > handles > dependencies, pre and post install issues, etc. in a > logical way - if > logic can even be applied! > > 3. having a system that provides flexible > installation. For example, > some users will want to run a command that will > install the package > and every dependency automatically. Others will want > a command that > just installs just one or a few packages, but not > others perhaps. > Finally, many users want to just download individual > packages and > install them after they can understand what each is > going to do to > their systems. > > There are probably hundreds of other things to worry > about. I would > love to have a fairly detailed summary of your > methods for your > current software in GNOME/JDS and maybe an example or > two of how you > might add a new software package. For instance, > there are programs > like say nessus or nedit (that I don't think are > packaged at Sun) that > use GTK+ 2. How might such a progam be built and > packaged using what > you do now? > > People who use other methods can provide similar > examples. I think > the more examples we have, the easier it will be for > us to at least > experiment, if not select one to use at this point. > > Just an idea. > > Steve C. > > On 8/17/05, Glynn Foster <[EMAIL PROTECTED]> > wrote: > > Hey, > > > > > First, my thanks to Dennis for his very kind and > supportive comments. > > > I have always enjoyed, and will continue to > enjoy, working with him > > > and the members of Blastwave. I fully expect to > have our individual > > > communites join together with the OpenSolaris > world of develpers to > > > define and deploy the large "external > tools/applications" software > > > part of this effort. There are many things to > plan and create and we > > > all hope this can be done quickly and cleverly by > the community. > > > > This is totally cool. I just want to add my support > to you guys - let me > > know if there's anything the GNOME/JDS team can do > to help out. We're > > very keen on being able to share a lot of the > software stack that GNOME > > depends on - it'll definitely make our lives easier > if there are already > > some packages available, and a unified solution > just gives me a warm > > fuzzy. > > > > Any thoughts for creating a packaging community, or > is it too early to > > go that direction just yet? > > > > > > Glynn > > > > > _______________________________________________ > opensolaris-discuss mailing list > [email protected] > This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
