On 8/22/2010 4:51 PM, John Plocher wrote:
If you build a distro and make the resulting binaries (an ISO
image...) available on a website, all you need to do is provide a
compressed tar file (or an ISO image of one) of the "make clean"d
source tree you used - there is no reason to make the source tree part
of your binary ISO image....
Since the source tree tar file will be large (and not very interesting
as time marches on), a better way is to provide a pointer to the same
IllumOS or Oracle or ... versioned mercurial repository that *you*
started with and make a gzipped file of just your "diffs" ('hg export'
or 'hg merge' as appropriate). An interested developer could then
grab the common/unchanged sources from the same place you did, apply
your changes and build their own copy.
The goal is to make it so that someone else could build on your
changes in the same way you built on the work of others.
-John
John's right. Another note here: when I originally said you need to
"make available" source for everything covered by the CDDL, I wasn't
specific enough. What I should have said was "you need to make
available all source for CDDL'd code *should someone ask for it*". In
plain English: you can distribute the binaries by themselves. However,
as part of the distro image, you should have a README or similar file
which says "if you want the source for this stuff, get it here" and
point to the various repos (which, as John indicated, can be a
combination of stuff you maintain and/or someone else maintains).
--
Erik Trimble
Java System Support
Mailstop: usca22-123
Phone: x17195
Santa Clara, CA
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
