Date: Mon, 04 Feb 2013 11:00:59 -0600 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: Micheas Herman <m@micheas.net> Cc: FreeBSD Ports List <freebsd-ports@freebsd.org> Subject: Re: I need help with git Message-ID: <0443BE287B6E84CF0E0690FA@utd71538.campus.ad.utdallas.edu> In-Reply-To: <CAJw6ijnmkjiRb=BkbH0k-zDmPoxhUVVTiCsqVf_ZNgQQGnOUVg@mail.gmail.com> References: <39A84EC03A29CF90A1609C44@utd71538.campus.ad.utdallas.edu> <CAJw6ijnmkjiRb=BkbH0k-zDmPoxhUVVTiCsqVf_ZNgQQGnOUVg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--On February 4, 2013 8:33:06 AM -0800 Micheas Herman <m@micheas.net> =
wrote:
>
>
> On Monday, February 4, 2013, Paul Schmehl wrote:
>
> I'm the maintainer for security/barnyard2. =C2=A0The software recently
> changed so that all distros are pulled from github. =C2=A0The 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=3D =C2=A0 =C2=A0 =C2=A0 barnyard2
> PORTVERSION=3D =C2=A0 =C2=A01.11
> CATEGORIES=3D =C2=A0 =C2=A0 security
>
> MAINTAINER=3D =C2=A0 =C2=A0 pauls@utdallas.edu
> COMMENT=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0Interpreter for Snort unified2 =
binary output files
>
> LICENSE=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0GPLv2
>
> USE_GITHUB=3D =C2=A0 =C2=A0 yes
> GH_ACCOUNT=3D =C2=A0 =C2=A0 firnsy
> GH_PROJECT=3D =C2=A0 =C2=A0 ${PORTNAME}
> GH_TAGNAME=3D =C2=A0 =C2=A0 master
>
>
>
>
> You need to change th GH_TAGNAME to the release you want if you go to the
> repository on=C2=A0github 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=20
thanks. I'll abandon it first. This is volunteer work. I'm not going to=20
double my workload just because the system changed and doesn't work as=20
expected.
>
> =C2=A0
>
> GH_COMMIT=3D =C2=A0 =C2=A0 =C2=A04dfdc80
>
>
>
>
>
>
> Probably not needed if you specify a tag other than master.=C2=A0
>
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=20
v2-${PORTVERSION}. Now it pulls the commit for the release version as=20
desired.
--=20
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0443BE287B6E84CF0E0690FA>