> 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
Lawrence Velázquez writes:
> On Aug 23, 2014, at 7:25 AM, Vincent 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 which case, ye
On Aug 23, 2014, at 7:25 AM, Vincent 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 which case, yes, that would make
> sense.
http:
> Yes, specifying a version or date in the version line when fetching from a
> VCS is cosmetic, and is assumed to be in addition to another mechanism for
> informing the VCS what commit of code should be checked out.
Ok, will try and keep you posted.
Thanks again!
_
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
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.
Th
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 re
On Aug 22, 2014, at 11:43 AM, Simon Newton wrote:
> Can someone take a look at this please. It looks like the maintainer is
> absent.
I'm looking at it; I'll add a note in the ticket.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
htt
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
Ryan Schmidt wrote:
rpm5x: replace with 5.4.x
>>>
>>> This is not sufficient to replace a port. For the proper procedure, see
>>> https://trac.macports.org/wiki/PortfileRecipes#replaced-by
>>
>> Well, it would be OK for any users of the old ports to keep using them.
>> Instead of adding th
10 matches
Mail list logo
