On Wed, Jul 02, 2008 at 06:49:25PM +0200, Vincent Beffara wrote:
>
> Nevertheless, the general question is interesting in itself. What to do
> if one wants to follow the SVN version of a package ? Can one assume
> that the build machine will have network access ? (It kind of has to
> if only to do
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 ...
> >
> >
Alexander Hansen wrote:
> On Thursday 03 July 2008 09:36:20 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 serv
> > > > (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 so
On Thursday 03 July 2008 09:36:20 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
> > (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
>
Vincent Beffara wrote:
> Hi,
[]
> I am interested in something similar myself, and thought essentially of
> two solutions :
>
> (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
Hi,
> > One option is to make a tarball up and post it somewhere until the mirrors
> > pick it up.
>
> That's what I've done for now. Glad to know that was ok :)
Nevertheless, the general question is interesting in itself. What to do
if one wants to follow the SVN version of a package ? Can one
On Wed, Jul 02, 2008 at 12:10:26PM -0400, Alexander Hansen wrote:
> One option is to make a tarball up and post it somewhere until the mirrors
> pick it up.
That's what I've done for now. Glad to know that was ok :)
---
James
pgpPUTMtUcD9G.pgp
Description: PGP signature
---
On Wednesday 02 July 2008 11:39:07 James Bunton wrote:
> Hi all,
>
> As you may know, the current PyObjC 1.4 in Fink doesn't build on
> Leopard. While PyObjC 2.0 is included in OSX Leopard's system python it
> would be nice to have in Fink also. That way an application can use
> Fink's python libs
Hi all,
As you may know, the current PyObjC 1.4 in Fink doesn't build on
Leopard. While PyObjC 2.0 is included in OSX Leopard's system python it
would be nice to have in Fink also. That way an application can use
Fink's python libs as well as PyObjC.
This package is of SVN revision 2008 from
htt
11 matches
Mail list logo
