On Apr 22, 2012, at 20:05, Bradley Giesbrecht wrote: > On Apr 22, 2012, at 1:36 PM, Ryan Schmidt wrote: > >> >> On Apr 22, 2012, at 11:26, Daniel wrote: >> >>> Except some people still use snowleopard and as far as I could tell, ipfw >>> is still a valid command on Lion. Is it just ignored or can it still be >>> configured? If it's the latter, there's another reason for it to stay >>> enabled. >>> >>> I would have preferred to see ONE sshguard port with variants. >> >> Even better: ONE sshguard port, with no variants, that knows which OS X >> versions have ipfw and which have pf and selects the correct one >> automatically. And I believe that's what we already have. Try it out. > > > Thanks Ryan. What about upgrades from pre-Lion to post-SL.
> Is there an example port that has some sort of platform/os.version block that > can trigger an upgrade? What do you mean? Whether via install or upgrade, the new sshguard port will choose the correct configure.args based on the version of OS X. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
