From owner-freebsd-ports@FreeBSD.ORG Thu Nov 5 00:21:29 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0612D106566B for ; Thu, 5 Nov 2009 00:21:29 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id 8E5648FC0A for ; Thu, 5 Nov 2009 00:21:28 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id nA4NidZn069151; Wed, 4 Nov 2009 17:44:39 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id nA4Nidee069150; Wed, 4 Nov 2009 17:44:39 -0600 (CST) (envelope-from brooks) Date: Wed, 4 Nov 2009 17:44:38 -0600 From: Brooks Davis To: Eitan Adler Message-ID: <20091104234438.GB42953@lor.one-eyed-alien.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gj572EiMnwbLXET9" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 04 Nov 2009 17:44:39 -0600 (CST) Cc: ports@freebsd.org Subject: Re: using svn to fetch for ports (yet again!) 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: Thu, 05 Nov 2009 00:21:29 -0000 --gj572EiMnwbLXET9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 04, 2009 at 08:23:02PM +0200, Eitan Adler wrote: > I have a small patch to bsd.port.mk which would allow a port to > replace its do-fetch with a svn export of a /specific revision/ of a > remote repo. >=20 > I know there have been some attempts at trying this before and from > what I've been reading I addressed some of the major concerns: > 1) Past attempts didn't include a basic implementation. > 2) Past attempts didn't allow for a specific revision number and thus > possibly causing security issues > 3) Subversion does not have to be part of the base system for my patch to= work >=20 > Allowing the port to fetch from svn is beneficial for a number of > reasons some of which are listed below > 1) Many project's only or main means of distribution is svn (I'm > thinking of mplayer) > 2) It is easier for the port maintainer to update the port > 3) It is easy for a user to quickly switch versions (outside of the > ports system) without the need for lots o knowledge about the ports > system >=20 > Some of the problems: > 1) Its harder if not impossible for freeBSD to mirror the port's > source (I'm sure I could easily code a svn-to-tarball script but who > knows if the svn build servers want svn) > 2) Many users may want the program they are installing but not svn > 3) What about SCM's other than svn? I'd much rather see this used as something that reduced the amount of code required for maintainers to build tarballs from SVN. For example something similar in spirit to what I've done in devel/llvm-devel. That means mirroring or otherwise transfering the source around is possible. There will likely be some objections to putting maintainer functionality in bsd.port.mk, but I think it would be useful enough in this case. Alternativly we could formalize the process a bit and put something Tools/scripts. -- Brooks --gj572EiMnwbLXET9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFK8hHmXY6L6fI4GtQRAmmBAKCM7idIWEYHokM1DKTB0WVNGNRT0ACeIH3v hsEwAQl9LxYiqNBG5XuXOFY= =WMj+ -----END PGP SIGNATURE----- --gj572EiMnwbLXET9--