Max Horn wrote:
> Am 20.01.2007 um 17:53 schrieb Jack Howarth:
[]
>> What is the recommended form for the Source line when
>> the source tarball only exists within the fink mirror
>> system?
>
> Unless somethign dramatic changed while I wasn't watching (which is
> easily possible, considering I
Am 20.01.2007 um 17:53 schrieb Jack Howarth:
> David,
>Currently I have...
>
> Source: mirror:custom:pymol/pymol-0_99rc8-src.tgz
> CustomMirror: <<
> Primary: http://easynews.dl.sourceforge.net/sourceforge
> <<
>
> What is the recommended form for the Source line when
> the source tarball onl
David,
Currently I have...
Source: mirror:custom:pymol/pymol-0_99rc8-src.tgz
CustomMirror: <<
Primary: http://easynews.dl.sourceforge.net/sourceforge
<<
What is the recommended form for the Source line when
the source tarball only exists within the fink mirror
system? Also, I think we should a
I've read through the Pymol license, which permits the source code to
be redistributed.
That means the correct way to handle this in fink is as follows: the
fink package manager does the SVN checkout, strips out SVN stuff, and
creates a tarball. We then host that tarball on the fink site (o
I like pymol and I pay for using it, but I think it is no longer
effectively open-source if it can't be readily downloaded.
The current fink version of pymol is essential to me because it provides a
free way of using a free electrostatics program (apbs) and there are no
other alternatives, so even
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 pas
The problem with diffs is that I believe he ships binary files
that change as well. 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
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 commen
I noticed this week that a new pymol 0.99rc8
version was released but starting with that
version no source tarball would be made available
on pymol.sourceforge.net. Rather users will have
to manually access the source via svn in an effort
to limit the ease of packaging this open source
software.
