Date: Tue, 5 Feb 2013 08:57:20 -0500 From: Wesley Shields <wxs@FreeBSD.org> To: Shane Ambler <FreeBSD@ShaneWare.Biz> Cc: Paul Schmehl <pschmehl_lists@tx.rr.com>, Micheas Herman <m@micheas.net>, FreeBSD Ports List <freebsd-ports@freebsd.org> Subject: Re: I need help with git Message-ID: <20130205135720.GB4031@atarininja.org> In-Reply-To: <511059BB.5000203@ShaneWare.Biz> References: <39A84EC03A29CF90A1609C44@utd71538.campus.ad.utdallas.edu> <CAJw6ijnmkjiRb=BkbH0k-zDmPoxhUVVTiCsqVf_ZNgQQGnOUVg@mail.gmail.com> <511059BB.5000203@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
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 to pull? > > I think the thing most people miss here is that GH_COMMIT doesn't > effect what gets downloaded, it's not used like an svn rev number > - it is only used to define WRKSRC > > When a github tarball gets extracted GH_COMMIT is part of the dir name. > > Which is why it is mandatory and needs to match the tag. It is just > needed to work with the way github creates tarballs. It is inconvenient > but github is only setup to let you download tarballs of specific tags > not specific commits. If the main devs don't tag the specific points you > want the only option is to fork and create your own tags. 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 234fd5bab1225e483ea263a5a15faebed0bd61b9: https://github.com/ironbee/libhtp/archive/234fd5bab1225e483ea263a5a15faebed0bd61b9.tar.gz -- WXS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130205135720.GB4031>