On 03/16/2013 06:37 PM, Mr Dash Four wrote: > >> As it stands, /usr/libexec/shorewall-init/ifupdown (from Fedora's >> perspective) is copied to /sbin/ifup-local as well as >> /sbin/ifdown-local. Wouldn't it be better to create a symlink to >> /usr/libexec/shorewall-init/ifupdown instead (/usr/libexec/* can be >> executed, so I don't think there would be any SELinux alerts in that >> respect)? > Further to this: what is the reason for not creating these two files as > part of the shorewall-init package instead? > > It would be much easier for rpm to track the file changes that way > (during install/upgrade/delete) instead of mucking about with %post and > %postun scripts, don't you think?
The Shorewall-init RPM is installable on both RedHat-based and SusE-based systems, and the two have very different requirements. I would expect that distribution-specific .spec files would do as you suggest (and also create symbolic links if appropriate). -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
