From owner-freebsd-ports@FreeBSD.ORG Mon Jun 18 09:28:44 2007 Return-Path: X-Original-To: ports@FreeBSD.org 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 78AE716A468 for ; Mon, 18 Jun 2007 09:28:44 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from misav07.sasknet.sk.ca (misav07.sasknet.sk.ca [142.165.20.171]) by mx1.freebsd.org (Postfix) with ESMTP id 33F0513C448 for ; Mon, 18 Jun 2007 09:28:43 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from bgmpomr1.sasknet.sk.ca ([142.165.72.22]) by misav07 with InterScan Messaging Security Suite; Mon, 18 Jun 2007 03:28:43 -0600 Received: from server.hurd.local (adsl-76-202-204-41.dsl.lsan03.sbcglobal.net [76.202.204.41]) by bgmpomr1.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0JJT00F1IRNUA600@bgmpomr1.sasknet.sk.ca> for ports@FreeBSD.org; Mon, 18 Jun 2007 03:28:43 -0600 (CST) Date: Mon, 18 Jun 2007 02:28:41 -0700 From: Stephen Hurd In-reply-to: <8623CF89-858D-4524-9B4A-9147913739F3@brooknet.com.au> To: Sam Lawrance Message-id: <46765049.3080605@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <4673B0DB.3040100@sasktel.net> <46742CF6.3050901@sasktel.net> <20070616202819.GA29331@rot13.obsecurity.org> <4674572D.9060707@sasktel.net> <8623CF89-858D-4524-9B4A-9147913739F3@brooknet.com.au> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.2) Gecko/20070523 SeaMonkey/1.1.1 Cc: ports Subject: Re: Clarification on fetch/extract targets 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: Mon, 18 Jun 2007 09:28:44 -0000 Sam Lawrance wrote: > > On 17/06/2007, at 7:33 AM, Stephen Hurd wrote: > >> Kris Kennaway wrote: >>>> Actually, I found it quite easy to have the port pull the sources >>>> from svn. Who are we concerned about making it easier for and why >>>> (and how is it any easier?) >>>> >>> >>> Everyone behind a firewall that only allows fetching via HTTP/FTP, for >>> one. Also everyone without live network access, and those with >>> pay-per-download who have a free local distfile mirror, etc. >>> >>> Tarballs are overwhelmingly preferred. >>> >>> Kris >>> >> Ok... I was looking at it from the standpoint of someone who wants >> the newest version and doesn't care of the pkg-plist is stale. They >> could just bump PORTREVISION and reinstall. >> >> So... how about this: >> - A distfile target which generates a distfile. The idea being that >> this would be the one on the local distfile mirror or what have you. >> - A WITH_SVN option (defaults to off) which allows the end user to >> specify he/she wants to use the subversion. >> >> In this case then, the end user would need to bump PORTREVISION and >> enable the WITH_SVN option. > > Rather than suggesting that users change PORTREVISION, just suggest > that they set WITH_SVN and force an upgrade (eg. portupgrade -f > yourport). You mean have it just grab the current head no matter what when WITH_SVN is enabled? *shudder* All kinds of arguments against that spring to mind... - This is essentially an option to break the pkg-plist - The current trunk may not build/work/etc so the option will only work "sometimes" - The version number becomes wrong if a later update to the port increases the revision to something less than the current one, the tools will "upgrade" it to an older version These are just the ones that spring to mind initially... I'm sure there are other wild and crazy things that would/could happen.