On Thu, Jul 03, 2008 at 03:36:20PM +0200, Vincent Beffara wrote:
> > > (i) ship a base tarball that is close to the SVN trunk, and make a patch
> > > script that calls SVN to catch up to a prescribed revision number. The
> > > base tarball might be empty but it's not nice to the server ...
> >
> > An acceptable method (that has been used by some packages) is to get the
> > diff to an svn or cvs version and make a patch file from it.
> 
> Sure, that's doable, but it becomes quite tedious if you want to track a
> fast-moving project ... Are you implying that it is _not_ acceptable to
> call svn (or cvs or git or whatever) from the patch script ?

I'll state it explicitly: it is not acceptable to do network access in
any way during any part of a package-building except to download
sources via the Sources field.

In addition to the licensing concerns others mentioned regarding the
files being downloaded, there are functional issues. It prevents users
from downloading all the sources at a machine with fast connection and
then taking them home on a USB drive. It reduces traceability by not
using MD5 or other authentication in the .info (though with many
revision-systems, it's hard to change he content of a given
revision-number). By downloading all source files first (which is a
relatively fast operation for most users but also error-prone due to
network problems, etc) and then doing all the building, fink works
better unattended: would suck to have a long series of builds planned
to run while away die during the first pkg when the dialup connection
died briefly).

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel

Reply via email to