I need help with git

Paul Schmehl pschmehl_lists at tx.rr.com
Mon Feb 4 17:01:04 UTC 2013


--On February 4, 2013 8:33:06 AM -0800 Micheas Herman <m at micheas.net> 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, and I cannot figure out how to
> fix it.
>
> Here's the relevant code from the Makefile:
>
> PORTNAME=       barnyard2
> PORTVERSION=    1.11
> CATEGORIES=     security
>
> MAINTAINER=     pauls at utdallas.edu
> COMMENT=        Interpreter for Snort unified2 binary output files
>
> LICENSE=        GPLv2
>
> USE_GITHUB=     yes
> GH_ACCOUNT=     firnsy
> GH_PROJECT=     ${PORTNAME}
> GH_TAGNAME=     master
>
>
>
>
> You need to change th GH_TAGNAME to the release you want if you go to the
> repository on github and you can find the tags that the maintainers have
> added to the project.
>
>
> If you want a snapshot in time that is not tagged you could either
> request the authors tag it, or fork it on github tag it yourself and put
> your own account as the GH_ACCOUNT.
>

So now I have to maintain a git repository just to maintain my port?  No 
thanks.  I'll abandon it first.  This is volunteer work.  I'm not going to 
double my workload just because the system changed and doesn't work as 
expected.

>
>  
>
> GH_COMMIT=      4dfdc80
>
>
>
>
>
>
> Probably not needed if you specify a tag other than master. 
>

According to /usr/ports/Mk/bsd.sites.mk, GH_COMMIT is mandatory.

# In order to use GitHub your port must define USE_GITHUB and the following
# variables:
#
# GH_ACCOUNT    - account name of the GitHub user hosting the project
#                 default: not set, mandatory
#
# GH_PROJECT    - name of the project on GitHub
#                 default: ${PORTNAME}
#
# GH_TAGNAME    - name of the tag to download (master, 2.0.1, ...)
#                 default: ${DISTVERSION}
#
# GH_COMMIT     - first 7 digits of the commit that generated GH_TAGNAME
#                 (man git-describe(1))
#                 default: not set, mandatory
#

Never mind.  I finally figured it out.  I had to change GH_TAGNAME to 
v2-${PORTVERSION}.  Now it pulls the commit for the release version as 
desired.

-- 
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell



More information about the freebsd-ports mailing list