From owner-freebsd-ports@FreeBSD.ORG Wed Oct 3 03:31:20 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7926B106566C for ; Wed, 3 Oct 2012 03:31:20 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE628FC0A for ; Wed, 3 Oct 2012 03:31:20 +0000 (UTC) Received: by pbbrp8 with SMTP id rp8so10876045pbb.13 for ; Tue, 02 Oct 2012 20:31:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=TnKtZtTtXM8MYWL2vS3FU74xuiWNKlSEsjmdJ1AAl9Y=; b=TlcTVt400fomZugDqoQJmRu7KHdHs7zSLglu32r663ugSkE+9IWFCaSM7a70AbD1PR Wl+bPksd6hi4N+DtALFFaoJvDGf6COveedk1fvTdDMjZOej5QAC3byK9nqfs36LSE2lk 2X2s3x4gF18ecCj+yXDBRqQvJAt4fPq4f0W2I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=TnKtZtTtXM8MYWL2vS3FU74xuiWNKlSEsjmdJ1AAl9Y=; b=MkbpXiv7gCPG7vYyOl/RLA749cOc11IRzqhHGD3Eq7Ml3GfVOj8TLz/nqZTWnnro3z rAp/qN/tkSyDoTTlTP3iKY/tdGUVGW95XL65UO5mbyiFxxturV4xILDECA6oijJVL+Eu ke/ZUyDyLSqPzzPJTfo4jSYh9SEbjZcloXtOYEBeNw7MZgIUcZXiViyjAO71omiV/nxU Ne7GY5CVououiuTUb/E6mk8Vuh/otJaFr4YO2BRCRxtY6a18HRmW1tuC5ognuldxc1U1 x/k5Sgm0f/qiZZZxW31WAsibkX1st08t1ETLb3a4Ux6oDesg9Qh9Ct5SUY6CiyZ8imT5 UISA== Received: by 10.68.200.231 with SMTP id jv7mr9316004pbc.140.1349235079681; Tue, 02 Oct 2012 20:31:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.190.164 with HTTP; Tue, 2 Oct 2012 20:30:49 -0700 (PDT) In-Reply-To: <267E4790564988D2A545BF49@Pauls-MacBook-Pro.local> References: <6DE237A2D4133FBAED25FC26@localhost> <44626syfjv.fsf@be-well.ilk.org> <17F1F6096650E45134B198CD@localhost> <85CE784EEB463CD1C26E6C06@localhost> <20121002232812.442d2c20@bsd64.grem.de> <267E4790564988D2A545BF49@Pauls-MacBook-Pro.local> From: Eitan Adler Date: Tue, 2 Oct 2012 23:30:49 -0400 Message-ID: To: Paul Schmehl Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQk9Uh/ruL6XetDDtRI7bGvOLnebMdLrbp8gm6tE6FK/D21+8lvcGjLi9VJLwlY6RBI4iEZX Cc: freebsd-ports@freebsd.org, Michael Gmelin Subject: Re: How to check out ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2012 03:31:20 -0000 On 2 October 2012 22:54, Paul Schmehl wrote: > --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. Looks like the git hash: use GH_ACCOUNT GH_PROJECT and GH_COMMIT (see bsd.sites.mk for details) -- Eitan Adler