Le 24 août 2014 à 18:53, Sean Farley s...@macports.org a écrit :
Why not use the bitbucket port group?
PortGroup bitbucket 1.0
bitbucket.setup petebunting rsgislib 52fb22e
version 0.0.20140822
Uh, I just didn’t know there was a bitbucket group. Sorry for being
Le 24 août 2014 à 18:53, Sean Farley s...@macports.org a écrit :
Why not use the bitbucket port group?
PortGroup bitbucket 1.0
bitbucket.setup petebunting rsgislib 52fb22e
version 0.0.20140822
Uh, I tried that and it works (fetch okay), but then I have a problem.
Vincent Habchi writes:
Le 24 août 2014 à 18:53, Sean Farley s...@macports.org a écrit :
Why not use the bitbucket port group?
PortGroup bitbucket 1.0
bitbucket.setup petebunting rsgislib 52fb22e
version 0.0.20140822
Uh, I tried that and it works (fetch okay),
Le 25 août 2014 à 20:07, Sean Farley s...@macports.org a écrit :
There are a few ways to work around this. In the dolfin port, I do:
configure.dir ${worksrcpath}/build
build.dir ${worksrcpath}/build
Thanks, that works like a charm. I’ll commit the ports now.
Vincent
From the command line, you can use revsets:
$ hg log -G -r 'date(2014-08-22)'
On the MacPorts repo, that will result in a lot of changesets. For a
portfile, you really must specify a commit hash.
I suppose that’s what I did, but since you seem to master Mercurial much better
than me
Vincent writes:
From the command line, you can use revsets:
$ hg log -G -r 'date(2014-08-22)'
On the MacPorts repo, that will result in a lot of changesets. For a
portfile, you really must specify a commit hash.
I suppose that’s what I did, but since you seem to master Mercurial much
Hi there,
I have completed the Portfile for two new libraries I could eventually add to
our already swell collection. Except that these two ports, out of which one
depends on the other, are not official releases but trunk versions. In fact,
official releases do exist, but they are outdated and
On Aug 23, 2014, at 5:41 AM, Vincent wrote:
I have completed the Portfile for two new libraries I could eventually add to
our already swell collection. Except that these two ports, out of which one
depends on the other, are not official releases but trunk versions. In fact,
official
Hi Ryan,
My opinion would be that you can add the ports this way, with their
development versions, without any special notice, since it sounds like their
latest stable versions will not work the way you need them to work. You can
make up a version number to put in the version field.
That
On Aug 23, 2014, at 6:25 AM, Vincent wrote:
My opinion would be that you can add the ports this way, with their
development versions, without any special notice, since it sounds like their
latest stable versions will not work the way you need them to work. You can
make up a version number
Lawrence Velázquez writes:
On Aug 23, 2014, at 7:25 AM, Vincent vi...@macports.org wrote:
However, I’ll have a look a ‘mercurial’ (unless someone out there is a guru
of this yet-another-DRC and can advise me directly) to figure out if there
is a way to specify a date as a revision. In
11 matches
Mail list logo
