On 7/14/05, Joerg Schilling <[EMAIL PROTECTED]> wrote:
So we should put on the list for the OpenSolaris/Solaris OpenSource unification Community(name subject to change, since i just made it up ;-) ) as a charter member?
where you will commit changes to packages back to the community for the good of all.
of course we should create some guide lines like.
- only minimal changes to Makefile(s), and the ones that are should make it easier to configure the target location for binaries and libraries.
- keep changes that are specific to your distrobution in a directory inside the package, if many changes are made that are distrobution specific, perhaps a script that can reproduce them included in this directory thus making the work of whole less.
these are just a couple i just thought up, they are of course up for discussion.
James Dickens
uadmin.blogspot.com
Joost van Baal <[EMAIL PROTECTED]> wrote:
> > Blastwave
> > Pkgsrc
> > SchillyX
> > SunFreeware
> > Sun
> >
> > Currently all each group has to download and port each package they
> > distribute; there is no sharing of code. All 4 groups strive to have a high
> > level of quality in there code. Yet each group currently serves a different
> > segment of the Solaris community. There are still others that run Solaris
> > that are not really met by any of these solutions and need the source.
> >
> > What I propose is that all 5 groups work together, and create a community
> > cvs or source code manager that they can agree on, that holds the source and
> > changes to Open Source Software they distribute.
> <snip>
>
> FWIW: A first step could be to publish sources of packages, like Debian
> source packages, or SRPMs, or *BSD ports. One idea implementing this
> for Solaris packages is at http://mdcc.cx/csbs/ .
>
> But I guess the problem you mention is not just a technical problem, but
> for the major part a social problem. These are much harder to tackle...
> :)
For some people it may be a social problem. For me it is only a matter of time.
For SchilliX, there is already SPS that has been carefully tested and allows you
to compile every SPS package that has been published on OpenSolaris. There is a
single exception: X11
The fact that not yet everything is available as SPS packages is just a result
of the fact that I don't publish packages that do not yet compile on OpenSolaris.
I am publishing more and more compilable packages that allow to auto-create
tar archives with binaries that may be installed. I am currently expecting
to be ready to publish all sources for SchilliX-0.3.
So we should put on the list for the OpenSolaris/Solaris OpenSource unification Community(name subject to change, since i just made it up ;-) ) as a charter member?
where you will commit changes to packages back to the community for the good of all.
of course we should create some guide lines like.
- only minimal changes to Makefile(s), and the ones that are should make it easier to configure the target location for binaries and libraries.
- keep changes that are specific to your distrobution in a directory inside the package, if many changes are made that are distrobution specific, perhaps a script that can reproduce them included in this directory thus making the work of whole less.
these are just a couple i just thought up, they are of course up for discussion.
James Dickens
uadmin.blogspot.com
Now let me discuss the other binary package sources:
Blastwave A currently binary only distributuion. As we need to install a
lot of the software in /usr instead of /opt/swf, it is currently
not delivering output that could be used for OpenSolaris
Pkgsrc I am still waiting to see any proof for the rumors that people
have been able to run it on OpenSolaris. I believe that it
is most unlikely that Pkgsrc will currently be usable on
OpenSolaris. Note that running on OpenSolaris is different
from running on Sun Solaris.
SunFreeware seems to have a lot in common with Blastwave
Sun Sun does not yet provide any sources (besides OpenSolaris
itself) that compile out of the box on OpenSolaris.
For /usr/sfw/bin, there are sources but the build system is
missing. For the packages that are under GPL, this is a
violation of the GPL.
I downloaded the JDS Sources last week. It took me ~ 300
mouse clicks to download 74 packages in "pkgadd" format.
As there is no 'pkgadd' on OpenSolaris, it will most likely
take more than a day to only unpack the sources. I am sure
that there are more than a dozen other packages currently
missing on OpenSolaris that JDS compilation depends on.
I hope that this short review will help to understand the problems of us
OpenSolaris developers.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
