On 6/02/2013 8:59 PM, Shane Ambler wrote:
> On 06/02/2013 00:27, Wesley Shields wrote:
>
>> I don't know if we have a way to express this in the ports framework but
>> you absolutely can grab a tarball of a repo at any specific commit on
>> github even if it is not tagged.
>>
>> This is the URL to
On 06/02/2013 00:27, Wesley Shields wrote:
I don't know if we have a way to express this in the ports framework but
you absolutely can grab a tarball of a repo at any specific commit on
github even if it is not tagged.
This is the URL to grab ironbee/libhtp at
234fd5bab1225e483ea263a5a15faebed0
On Tue, Feb 05, 2013 at 11:30:43AM +1030, Shane Ambler wrote:
>
> >
> >> GH_COMMIT= 4dfdc80
> >
> > Probably not needed if you specify a tag other than master.
>
> >> If I pull master, I get commit f57e464. That's not what I want.
> >> Why doesn't this thing pull the commit I'm telling it t
GH_COMMIT= 4dfdc80
Probably not needed if you specify a tag other than master.
If I pull master, I get commit f57e464. That's not what I want.
Why doesn't this thing pull the commit I'm telling it to pull?
I think the thing most people miss here is that GH_COMMIT doesn't
effect wh
--On February 4, 2013 11:41:45 AM -0500 Greg Larkin
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/4/13 11:21 AM, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers
made new comm
--On February 4, 2013 5:36:02 PM +0100 Michael Gmelin
wrote:
Hi Paul,
Could you revisit what I write to you about this a couple of months ago?
I just tried changing GH_TAGNAME to v2-1.11 in Makefile and it just
worked fine (by the way, that's what I suggested back then, you should
never depen
On Mon, 04 Feb 2013 10:21:35 -0600
Paul Schmehl wrote:
> I'm the maintainer for security/barnyard2. The software recently
> changed so that all distros are pulled from github. The developers
> made new commits, and now the port is broken, and I cannot figure out
> how to fix it. Here's the rele
--On February 4, 2013 8:33:06 AM -0800 Micheas Herman wrote:
On Monday, February 4, 2013, Paul Schmehl wrote:
I'm the maintainer for security/barnyard2. The software recently
changed so that all distros are pulled from github. The developers made
new commits, and now the port is broken, an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/4/13 11:21 AM, Paul Schmehl wrote:
> I'm the maintainer for security/barnyard2. The software recently
> changed so that all distros are pulled from github. The developers
> made new commits, and now the port is broken, and I cannot figure
> out
On Monday, February 4, 2013, Paul Schmehl wrote:
> I'm the maintainer for security/barnyard2. The software recently changed
> so that all distros are pulled from github. The developers made new
> commits, and now the port is broken, and I cannot figure out how to fix it.
>
> Here's the relevant
On Mon, Feb 4, 2013, at 11:21 AM, Paul Schmehl wrote:
> I'm the maintainer for security/barnyard2. The software recently changed
> so that all distros are pulled from github. The developers made new
> commits, and now the port is broken, and I cannot figure out how to fix
> it.
>
I am no git
I'm the maintainer for security/barnyard2. The software recently changed
so that all distros are pulled from github. The developers made new
commits, and now the port is broken, and I cannot figure out how to fix it.
Here's the relevant code from the Makefile:
PORTNAME= barnyard2
PORTV
12 matches
Mail list logo