Date: Thu, 27 Sep 2012 19:23:58 +0200 From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= <decke@bluelife.at> To: mexas@bristol.ac.uk, freebsd-ports@freebsd.org Subject: Re: redports - should I rename the updated distfile (tarball)? Message-ID: <1348766638.1490.2.camel@Nokia-N900-42-11> In-Reply-To: <201209271155.q8RBtpgG001020@mech-cluster241.men.bris.ac.uk> References: <201209271155.q8RBtpgG001020@mech-cluster241.men.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Do., 27. Sep. 2012 13:55:51 CEST, Anton Shterenlikht <mexas@bristol.ac.uk> wrote: > redports.org is good, thank you to whoever worked on it. You're welcome. > One question: the upstream for my port is non-existent, > so rather then patch it, I'm updating the code itself. > I then create a new tarball. It seems redports doesn't > update the tarball every time I request a build. > So it seems I have to update the version in Makefile > each time and create a tarball with this new number. > Is that so? Redports uses a distfile cache so it only tries to download the distfile if it's not in the cache of that build machine yet. You could try to check bsd.ports.mk if there is a target that you can overwrite in your port where it does the distfile check. -- http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1348766638.1490.2.camel>