The summary says it all :) The developer published a bugfix 4.0.9.1 which already hit the download mirrors. A simply ebuild copy from 4.0.9 should be enough. Thanks for your fast response/reaction to the last bug #211191 !!! :) Reproducible: Always
CC, maintainer. Vieri, advice, please.
Created attachment 144735 [details, diff] shorewall-perl patch It's the simplest way to grab the latest "patches". If someone comes up with a nicer method... (like copying the ebuild to 4.0.9.1 but then changing the RDEPEND dynamically with sed or similar so that it validates -common-4.0.9) Anyway, it emerges fine. The only glitch is that the user will not know which upstream shorewall-perl version is to be installed until after it has been emerged and one issues a "shorewall version -a". Unless of course the -r ebuild revisions correlate to the patch versions but that may not happen. But on the other hand, they really are patches, not software releases, although upstream is making it also available as a package. So I think that this method is simple and easy to update, unless someone comes up with a cool sed one-liner. :)
(In reply to comment #2) > It's the simplest way to grab the latest "patches". If someone comes up with a > nicer method... (like copying the ebuild to 4.0.9.1 but then changing the > RDEPEND dynamically with sed or similar so that it validates -common-4.0.9) Vieri, take a look at versionator.eclass. It contains everything you need, e.g. MY_P_TREE=$(get_version_component_range 1-2) MY_P_PATCH=$(get_version_component_range 4) It works in pure bash so it supposed to be faster then sed for such simple cases :) In any case shorewall-perl-4.0.9-r1.ebuild is in the tree. FIXED.
