On 1/19/07, Jack Howarth <[EMAIL PROTECTED]> wrote:
> The problem with diffs is that I believe he ships binary files
> that change as well.

I'm not suggesting diffs, though. You should be able to check out or
export the SVN tree to a local directory, then create a new tarball
from that. In the past, the Fink mirrors have hosted source tarballs
for packages that are hard to download automatically, so that might be
an option in this case.

> Even without handling the binary changes,
> the diff between 0.99r6 and 0.99r8 is around 3.5 mb. Also
> the diff approach would soon get out of hand where the patch
> would exceed the size of the source tree at some point.
> Warren has indicated he believes the svn exists for those
> who actively participate in pymol development which I take
> to be an extremely draconian interpretation of the open
> source philosophy.

I haven't downloaded the package to check the license text for pymol,
but on SF.net, pymol has been categorized under the CNRI Python
license. I highly doubt that SF.net would allow someone to change the
license to a commercial one while continuing development on the SF.net
infrastructure. IMHO the developer's preference does not take
precendence over the text of the license itself (unless the license
changes in future versions, which is opening up another can of worms).

IANAL, but creating a tarball of the SVN repository and distributing
it via the Fink mirror servers sounds perfectly acceptable under
paragraph 2 of the CNRI Python license ("a nonexclusive, royalty-free,
world-wide license to reproduce, analyze, test, perform and/or display
publicly, prepare derivative works, distribute, and otherwise
use..."). Hopefully the wording of the actual pymol license agrees
with this.

>                    Jack
>
> On Fri, Jan 19, 2007 at 10:29:08PM -0500, Charles Lepple wrote:
> > On 1/19/07, Jack Howarth <[EMAIL PROTECTED]> wrote:
> > >I suppose we could adjust the fink
> > >packaging to no longer use a source tarball
> > >but to use svn to download the particular
> > >release branch and purge the .svn files out
> > >to create a proper source tree. Any suggestions?
> >
> > I'll let others comment on the idea of not using a source tarball, but
> > you can use 'svn export' to either download a tree without the .svn
> > directories (good for one-off downloads), or copy an existing working
> > copy while omitting the .svn directories. The latter option will let
> > you still incrementally update your working copy, and the local 'svn
> > export' takes care of cleaning things up.
> >
> > --
> > - Charles Lepple
>


-- 
- Charles Lepple

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to