Date: Tue, 09 Sep 2008 09:35:24 +0930 From: Kris Kennaway <kris@FreeBSD.org> To: Brooks Davis <brooks@freebsd.org> Cc: Steve Franks <stevefranks@ieee.org>, freebsd-ports@freebsd.org Subject: Re: Making ports from source with weird download restrictions Message-ID: <48C5BDC4.7060102@FreeBSD.org> In-Reply-To: <20080908185627.GE20793@lor.one-eyed-alien.net> References: <539c60b90809081003t35ebd62p2f5e006a1270f066@mail.gmail.com> <20080908185627.GE20793@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: > As long as the license allows redistribution, we can host it on FreeBSD > infrastructure using MASTER_SITE_LOCAL. > >> 2) openocd - http://openfacts.berlios.de/index-en.phtml?title=Building_OpenOCD >> - this is a bit more sensible - there's a stable SVN repository for >> it, it's just that the only ports I've seen are on sourceforge, and >> come from release .tgz archives, not a SVN archive (although I've >> never gotten a broken version from the openocd SVN). If someone >> pointed me at a port that built from SVN instead of a .tgz, I'm sure I >> could get the port done. > > Doing an svn export in the fetch stage is possible, but probably not > ideal. In my devel/llvm-devel port I have a do-fetch target that > fetches a snapshot and makes a tarball out of it, but I only use that > for my own use and host a snapshot on the FreeBSD ftp servers for normal > users since a tarball allows users to do a make clean and retry without > having to fetch files again. Yes, this is the right way to do it. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48C5BDC4.7060102>