Hi Tom On Sun, Mar 22, 2015, at 08:06 AM, Tom Eastep wrote: > I could do what you suggest, but the installed product wouldn't work. > Each major distribution has a unique method for handling network > interface up/down processing, and Shorewall-init must be installed to > match that processing. The location and name of the scripts are > different for each distribution, as are the parameters passed to those > scripts. > > As a consequence, both the Shorewall-init installer and installed code > have distribution-dependent logic.
I'm okay with that. My goal is to simply get the selected/specified products 'installed', in a 'generic' layout, into a DESTDIR so I can continue to massage it as needed. Atm, there are a number of hoops I'm jumping thru (not 100% sure there's not a better way yet) to get there. So far, they includ (1) comment out the case HOST=linux "exit 1" so it doesn't just die if 'generic' (2) change - first_install="Yes" + first_install="" so that the install STOPS trying to "Synchronizing state for <product>.service with sysvinit using update-rc.d..." There are a couple of others I'm trying to straighten out right now. I understand the "distribution-specific" stuff. And that's perfectly reasonable when the goal is one pacakge for one distro. As useful as all the current distro-pkgs are, they're (a) not sync'd with one another, and (b) really hard to modify/build yourself. Sure, I get that my opinion may be different that others'. For me, there's NO advantage to having shorewall installed "into" each system, spread out across all its distro-specific directories and locations. In my case of many installs/distros, it's a nightmare to manage. It can be perfectly functional -- and easier to manage -- completely isolated to a "/opt/shorewall" or "/usr/local/shorewall", with me 'just having to then manually install systemd service files and change a bin/path or add a couple of links. My goal is "distribution AGNOSTIC" -- one single-version, generic install into a directory, without any automatied/automating assumptions, that *I* can then modify, per detected/target distro,when I modify/push multiple, different-distro shorewall configs. Actually, no assimptions of any kind. Just "put it" where my shorewallrc tells it to. This would be very useful. There are more distros, and distro-layouts, than just those currently handled by SW's "cases" -- including LFS, and 'personal preference'. I'm not suggesting cobbling up a super-intelligent change to code -- instead, just adding one completely dumbed-down option. No automated installations, checks, startup enables, etc. Just install the files into the dirs & filenams I spec in my shorewallrc.generic and leave the rest to me. Bottom line "wish"? If rcfile == "shorewallrc.generic", then do/check nothing other than install into rc-specified locations. Hanlon. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
