shorewall version bump
Hi, we already moved to shorewall-5.0.x (the latest version is available within portage!). Because the move from shorewall-4.6 to shorewall-5.0 isn't a big deal I don't plan to add another shorewall-4.6 version to the tree. If you cannot move to shorewall-5.0 for some reasons you can copy shorewall to your overlay and simply rename the latest shorewall-4.6 ebuild. In that case please share details why you cannot move. Please close this bug if you will take the upgrade to shorewall-5.0. If you don't post any reasons why we need another shorewall-4.6 release I'll close this bug as "WON'T FIX" next week.
I suggested updating to the latest 4.6 in order to eventually stabilize the last 4.6 version and leave 5 as ~. However, I personally don't mind using 5 because upstream considers it stable.
Forgot to close.