On Fri, 23 Feb 2007, Laszlo (Laca) Peter wrote:
On Fri, 2007-02-23 at 12:32 -0800, Stephen Hahn wrote:
Okay. So what's wrong with starting to build a spec file base
separately and when SFW is ready to use them, we merge the 2
together?
If changes need to be made to pkgbuild for this to happen, I'm
happy do so.
It depends on your objectives--if you're just hoping to offer packages
as an OpenSolaris effort, then a merge can be delayed indefinitely (as
it seems to have been in the past); if your aim is to offer a set of
binaries that get picked up by the distributions, as those of ON are,
I would suggest pursuing a merge as a primary objective. Which would
mean engaging with /os/projects/sfwnv/ and extending that effort's
output...
Yes, I'm just hoping to offer packages as an opensolaris effort.
Up-to-date packages that install in /usr and target Nevada.
Are distributions actually interested in picking up binaries of
external open source projects?
One of them does, MarTux gets F/OSS binaries from Blastwave.
Otherwise, no: BeleniX, Nexenta, and SchilliX produce their
own F/OSS binaries independently.
I would think that build recipes
are far more useful. Be they in any machine-readable format.
Definitely. And in the same vein they are more conducive to
the "appliance foundary" concept too -- e.g. the kind of
thing that Jason Williams said (earlier in this thread) that
his company needs.
Eric
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
