--- James Dickens <[EMAIL PROTECTED]> wrote:
> On 7/14/05, ken mays <[EMAIL PROTECTED]> wrote: > > > > > > > > --- Joerg Schilling > <[EMAIL PROTECTED]> > > wrote: > > > > > > > > I hope that this short review will help to > > > understand the problems of us > > > OpenSolaris developers. > > > > > > Jörg > > > > 1. Standard Naming convention for community built > > packages. > > 2. Directory for those packages. > > 3. Agreement on compiler flags to use. > > 4. Review of various Solaris provider sites for > > Solaris packages (get everyone on the same page). > > > > Can we do what Linux hasn't done yet. Yes. The thing > > no one has brough up yet is that Sunfreeware has a > > packaging setup for Sol 2.5->2.10. Not the 'one > > package fits all' scheme. So, we should review > that as > > well as well as the SPARCv9 inclusion of > binaries/libs > > within the same packages as SPARCv8. > > > I beleve the goal of this project isn't binary > support at this point, not > all distrobutions release binaries anyway. Lets > start with source > compatility so the work of one maintainer can be > utililized by all, instead > of having 6 people do the same job repeatedly. > Security patches are applied > once and all each maintainer has to do is execute > there customization script > or just recompile with there own arguments each time > a patch or new version > comes out. We can of course maintain multiple > versions of each package if it > is needed, each Group is still free to store there > binaries where they see > fit at this point, this is just the first step of > the process. But it can > cut most of the maintainers work in 1/2 or more. > > James Dickens > uadmin.blogspot.com <http://uadmin.blogspot.com> > > > Right now, I scanned the common distributors of > > Solaris packages and I didn't find a package for > > libxml2 => v2.6.17 for the GNOME 2.10.2 project. > So, > > this is another issue where we have to check with > the > > Solaris package maintainers to ensure some sort of > > update schedule to support a major application > package > > like JDS or GNOME 2.10.2. Also, if this replaces > Sun's > > SUNW package of libxml2 how does it affect all of > the > > dependent SUNW packages like libxslt? ;o> > > > > Don't want JDS crashing, now do we? > > > > Hope that helps, > > Ken Mays @ EarthLink, Inc. > > James, A good point you helped bring up is the repository of the source code for Solaris/OpenSolaris in which all of the package maintainers can share - instead of everyone (i.e. the Solaris/OpenSolaris package providers) having their own separate source repositories. This is where Linux and *BSD have fallen a bit short. Once you start pushing past a certain threshold of built packages (>200-500), your storage requirements of all of those source files and maintaining them just seems so BIG in scope. Genunix.org to the rescue? Hope that helps, Ken Mays @ EarthLink, Inc. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
