Am 29.09.2010 08:38, schrieb Andrew:
>   On 28/09/10 22:19, Martin Hejl wrote:
>> To me it sounds (if we want to stay in line with the terms of use with
>> SF), that we either do that (but then, what actually _is_ a "binary
>> releases made via our File Release System or any other project
>> resource" - to me, it sounds like there'd have to be a new source
>> tarball for every new package checked into CVS and made available via
>> the packages page - if there is one for Bering uClibc 4 - if not, I
>> guess one could argue that if CVS isn't good enough for providing
>> source code, it doesn't qualify as a binary release either. But I'm
>> not a lawyer....), or look for some other means of hosting the source
>> and binaries.
> IMHO - 'binary release' means new distro version, not further minor
> updates - which may be decided as parts of pre-release current version.
> And yes, CVS isn't ehough good
When I said "if CVS isn't good enough" I was referring to the part in 
the document at 
http://sourceforge.net/apps/trac/sitelegal/wiki/Controversial%20project%20hosting#SourceAvailability
 

that reads:

"The presence of matching source code within CVS does not meet our 
source availability requirements."

I wasn't referring to missing features in CVS, but rather that having 
source code in CVS isn't "good enough" to meet the SF requirements for 
source availability.

> - for ex., mercurial and AFAIK git and
> svn can provide snapshot tarballs for any specified commit.
That's nice - but I guess they can't automatically put them into the SF 
File Release System, which, if I read the page correctly, is where the 
tarball needs to be to meet the SF requirements.

But either way - I didn't mean to start a "which versioning system 
should we use" discussion, especially since it doesn't matter to the 
problem at hand - no matter which versioning system is used, the source 
tarballs still need to be uploaded into the File Release System.

Martin

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to