Comment from Dennis :
I don't want to get caught up in a rolling street fight but I do
have a qualified comment or two. I snipped liberally. See below.
<snippage>
>> > Some work in the system, and modify the autoconf/configure,
>> > makefiles and other files in a portable way that
>> > allows the changes to move back upstream. Others just
>> > package it up anyway they can, with no visibility to how it
>> > was done (CCD, SFW, Blastwave). Pkgsrc is about the only
>> > one that is visible, but that's cause it has to built. But
>> > most often, folks just fix it so it works for *them*, and just
>> > go on, letting the knowledge of how they fixed it inside their
>> > community (possibly of one, themselves) as opposed to
>> > sharing it with the Solaris community or the Source themselves.
>>
>> I'm pretty certain Blastwave will gladly share their
>> knowledge with anyone interested, and I'm also pretty
>> certain Dennis would take exception to what you just
>> wrote about Blastwave
>
> Actually, Dennis knows about this. And it's only recently that
> the code was more accessible (more so than most of the
> developers for questions).
This is an area being actively worked on. Ultimately one should expect to
pull down a svn ( Subversion ) tree publicly for any package. The code that
you receive on your workstation will be expected to compile with your
Solaris and Sun Studio environment given some basic constraints. This is a
bit of a holy grail but one that can be achieved.
At the moment we do have a large pile of source in the Subversion repository
but certainly not all. Perhaps 30% of the 1680+ packages. That figure is not
to be taken lightly because it represents some 500 packages and all their
sources. No we are not ready for instant local builds, yet.
The other holy grail, the quest, would be to have a source tree that can be
compiled nightly with every dependency and every binary created fresh for
the end user. This also means that SVR4 compliant packages are produced that
can then be installed directly and with all dependencies resolved on the
fly.
Some new tools and new thinking is required in order to really make things
easy for the "new user" within reason and it has been my five year vision to
achieve that goal. I think that the Blastwave project is maturing nicely.
Dennis Clarke
_______________________________________________
opensolaris-discuss mailing list
[email protected]
