[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Heads-up: brand new RPM version about to hit rawhide

On Sat, 2008-07-12 at 16:09 -0400, Jesse Keating wrote:
> On Sat, 2008-07-12 at 10:36 -0400, Doug Ledford wrote:
> > After the talk was over I spent some time talking to Jesse where I
> > pointed out to him that if you did away with the look aside cache for
> > tarballs, and instead used exploded source in a repo, that you could in
> > fact add new branches onto a repo for essentially zero cost and those
> > branches could be what's used by people to make spins.  That in this way
> > we could, for next to no additional burden, carry their sources for them
> > to satisfy the GPL and to allow them to more readily create and
> > distribute spins.  Obviously, this hasn't gone anywhere since then.
> I think you misunderstood the problem.  We already keep around the
> sources on our servers for eons and anybody can get to them.  The
> problem surrounds actual distribution, IE handing you an CD/DVD of
> binary rpms.  I either have to offer you a CD/DVD of corresponding
> sources in <insert vague nonlegal terms here> format, or provide you a
> written offer to provide the above that is good for the next 3 years, or
> pass along such written offer that I myself may have gotten.  Nobody has
> confirmed nor denied what that <vague nonlegal terms here> means, nor
> how long the 3year clock ticks on those formats, and whether or not
> directions on how to get the source from our public source repo is OK.
> We don't need any special changes to our source control system, other
> than the fact that our tags are mutable, but one can go back as far as
> our merged core/extras Fedora world goes and recreate sourcerpms which
> contain the verifiable upstream source and any of our patches that went
> on top of it, and a reasonable build script for re-generating the
> binary.
> The problem really lies with whether or not this would satisfy, as a
> written offer, the requirements under which we distribute or ask our
> ambassadors to distribute our binaries.

OK, well regardless, if this meets the requirements, then certainly an
immutably tagged exploded SCM would too (for far less space requirements
than all those tarballs in the look aside cache), and my point still
stands that it would be cheaper to allow people to hang their spin
sources inside our SCMs when using exploded source and branches than the
current way.

Doug Ledford <dledford redhat com>
              GPG KeyID: CFBFF194

Infiniband specific RPMs available at

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]