From owner-freebsd-ports@FreeBSD.ORG Wed Oct 3 02:55:34 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5EE31065670 for ; Wed, 3 Oct 2012 02:55:34 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.120]) by mx1.freebsd.org (Postfix) with ESMTP id 951108FC0C for ; Wed, 3 Oct 2012 02:55:34 +0000 (UTC) X-Authority-Analysis: v=2.0 cv=IuCcgcDg c=1 sm=0 a=+L5dYfeubEW4PLvjDgtIXQ==:17 a=WAZfUmVf-EkA:10 a=05ChyHeVI94A:10 a=kj9zAlcOel0A:10 a=ayC55rCoAAAA:8 a=C1tAZTZuCUMA:10 a=uyavkMrdAAAA:8 a=6I5d2MoRAAAA:8 a=NEAV23lmAAAA:8 a=94AN9kpc0Yiv96URgXcA:9 a=CjuIK1q_8ugA:10 a=bPFmGhFUX2MA:10 a=JGX6LFFZUg8A:10 a=+L5dYfeubEW4PLvjDgtIXQ==:117 X-Cloudmark-Score: 0 X-Originating-IP: 76.184.157.127 Received: from [76.184.157.127] ([76.184.157.127:55632] helo=[10.0.0.7]) by cdptpa-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id 16/F1-17657-8E8AB605; Wed, 03 Oct 2012 02:54:33 +0000 Date: Tue, 02 Oct 2012 21:54:31 -0500 From: Paul Schmehl To: Michael Gmelin , freebsd-ports@freebsd.org Message-ID: <267E4790564988D2A545BF49@Pauls-MacBook-Pro.local> In-Reply-To: <20121002232812.442d2c20@bsd64.grem.de> References: <6DE237A2D4133FBAED25FC26@localhost> <44626syfjv.fsf@be-well.ilk.org> <17F1F6096650E45134B198CD@localhost> <85CE784EEB463CD1C26E6C06@localhost> <20121002232812.442d2c20@bsd64.grem.de> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: How to check out ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2012 02:55:34 -0000 --On October 2, 2012 11:28:12 PM +0200 Michael Gmelin wrote: > > > On Tue, 02 Oct 2012 14:14:26 -0500 > Paul Schmehl wrote: > >> --On October 2, 2012 2:44:46 PM -0400 Eitan Adler >> wrote: >> > On 2 October 2012 14:37, Paul Schmehl >> > wrote: >> >> I obviously wasn't very clear. I'm a port maintainer. I need to >> >> update one of my ports. I used to do this by checking out the >> >> port into a purpose-created directory in which I would use cvs to >> >> make changes and test. After everything checked out, I would >> >> submit the diff. >> > >> > We need to be better about announcing these changes as not to >> > frustrate maintainers. :) >> > >> >> Now cvs isn't working, so how, as a port maintainer, do I check >> >> out a single port so I can update it and submit it in a PR? >> > >> > You should do things the same way you did before, but instead you >> > should use svn to checkout out your port. Note that 'module names' >> > no longer work so you must use the full name: >> > e..g., svn checkout svn://svn.freebsd.org/ports/head/editors/nano >> > >> > It may help to keep a folder of "ports-I-maintain" with the ports >> > you maintain checked out. Before you update them do "svn update *" >> > and to generate a diff do "svn diff foldername" >> I got on the wiki and figured out how to check ou the port using svn, >> but now I'm stuck again. This port has moved to github, and I don't >> have a clue how to download it in the Makefile. There's no mention >> of github in /usr/ports/Mk, so I assume the method hasn't even been >> written yet. The source is here: >> , but I don't see a tarball, >> and I don't know enough about ports to know if it's even possible to >> fetch it from github. > > Hi Paul, > > What about using the ZIP > > https://github.com/firnsy/barnyard2/zipball/master > > (this will give you the current master branch in a ZIP file) > > or a tarball > > https://github.com/firnsy/barnyard2/tarball/master > > If you want to keep things more stable (since the master branch might > change frequently and break your build), limit yourself to a specific > version. Fortunately this software is using tags for versioning, so > it's easy to get zips from github, e.g.: > > https://github.com/firnsy/barnyard2/zipball/v2-1.10 > > or if you prefer a tarball (which is usually nicer to have) > > https://github.com/firnsy/barnyard2/tarball/v2-1.10 > > Github provides tarballs (and zipballs) for all branches and tags. > > See also: > > https://github.com/blog/12-tarball-downloads > > Hope that helps How do I handle this? firnsy-barnyard2-v2-1.10-0-g2f5d496.tar.gz Is the string at the end (g2f5d496) auto-generated? If so, that's another problem. I guess something like this? Sheesh. What a PITA. PORTNAME= barnyard2-v2 PORTVERSION= 1.10 PKGNAMEPREFIX= firnsy- PKGNAMESUFFIX= -0-g2f5d496 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