From owner-freebsd-ports@FreeBSD.ORG Tue Oct 2 19:14:30 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 2378F1065670 for ; Tue, 2 Oct 2012 19:14:30 +0000 (UTC) (envelope-from prvs=61524dd80=pschmehl_lists@tx.rr.com) Received: from ip-001.utdallas.edu (ip-001.utdallas.edu [129.110.20.107]) by mx1.freebsd.org (Postfix) with ESMTP id E196B8FC16 for ; Tue, 2 Oct 2012 19:14:29 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiwFACc8a1CBbgogTmdsb2JhbAA0Ea49kDoBASOCawEBAQMBAQI1Aj8FCwsOChkBARMoGxQGE4d/BguoHYFMAoZOiD2GB4UcgycEgi9gA4hYimSVXQ X-IronPort-AV: E=Sophos;i="4.80,524,1344229200"; d="scan'208";a="105235804" Received: from zxtm01.utdallas.edu (HELO [129.110.200.11]) ([129.110.10.32]) by ip-001.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Oct 2012 14:14:27 -0500 Date: Tue, 02 Oct 2012 14:14:26 -0500 From: Paul Schmehl To: Eitan Adler Message-ID: <85CE784EEB463CD1C26E6C06@localhost> In-Reply-To: References: <6DE237A2D4133FBAED25FC26@localhost> <44626syfjv.fsf@be-well.ilk.org> <17F1F6096650E45134B198CD@localhost> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1995 Cc: Lowell Gilbert , FreeBSD Ports List 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: Tue, 02 Oct 2012 19:14:30 -0000 --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. -- 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