Date: Fri, 2 Dec 2011 23:10:10 GMT From: Dominic Fandrey <kamikaze@bsdforen.de> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/162996: games/ioquake3-devel: update s2064->s2202 Message-ID: <201112022310.pB2NAAW8039110@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/162996; it has been noted by GNATS. From: Dominic Fandrey <kamikaze@bsdforen.de> To: bug-followup@FreeBSD.org, kalten@gmx.at Cc: Subject: Re: ports/162996: games/ioquake3-devel: update s2064->s2202 Date: Sat, 03 Dec 2011 00:08:47 +0100 ports/162301 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/162301 I won't accept any patches until that has been submitted. I'm afraid I also made significant changes to the freebsd-patchset in the distfile for ports/162301. I suspect whatever changes you made will be incompatible if you based your changes on the patchset for r2064. There's no need to bump PORTREVISION, because SVNVERSION is part of the DISTVERSION. Also, if you update ioq3-devel you also need to update openarena and iourbanterror. Some advice under the assumption that you'll maintain ports in the future: Run "port test" or "port test -L", so you're certain you didn't forget to update the plist. Also it's a good idea to compile your changes into a single patch, so you don't burden committers with having to apply a bunch of patches, especially from different locations. As far as the master->slave port thing goes you dabbled into one of the more complex arrangements. I'd like to litter the thing with comments, but that's not usual for the ports and would probably be frowned upon (the tree is supposed to stay reasonable small). -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112022310.pB2NAAW8039110>