Hello Paul,
You can add the action.x files and the *_start file to
/var/lib/lrpkg/upnpd.list. The /etc/shorewall and
/etc/shorewall/start.d/ directories are owned by the shorewall
package so the other files in this directory should be saved by the
shorewall package itself. Look at the weblet package for an example
about a start.d setup.
I'm not sure how to implement the changes in /etc/shorewall/modules
and actions without "hurding" the shorewall package, but maybe you
can also do this in a start.d script.
About owning directories, I made a small change in the buildtool
setup of your package, you listed the contents of the /etc/linuxigd
directory in the upnpd.list. That means that no package owns the
directory /etc/linuxigd and the directory itself would be back-upped
in the etc.lrp package. I changed the upnpd.list file to this:
etc/default/upnpd
etc/init.d/upnpd
etc/linuxigd
etc/upnpd.conf
usr/sbin/upnpd
var/lib/lrpkg/upnpd.*
By adding the following line in buildtool.cfg:
<File>
Filename = etc/linuxigd/
Type = list
</File>
That means that upnpd is now the owner of the /etc/linuxigd directory
and all it's contents is saved in that package, except if some "foo"
package has something like this in the .list file:
....
etc/linuxigd/foo
....
In that case the foo file will get saved in the "foo" package.
As a sidenote, please don' t add the kernel ipt_owner kernel module
to the upnpd package itself. For use it should be documented that it
needs to be added to the modules.lrp package by an user. Adding it to
upnpd would mean that the package breaks when a kernel update is
done.
Eric Spakman
---------------------------------------------------------------------
Hi,
I'm packaging upnpd.lrp. I'd like to add a few user defined actions
to
shorewall to make integrating leaf and shorewall a bit easier. I'm
wondering what the best way to do this is...
currently I'm having the user add:
/etc/shorewall/action.allowinUPnP
/etc/shorewall/action.allowoutUPnP
/etc/shorewall/action.forwardUPnP
/etc/shorewall/start.d/upnpd_start
modify /etc/shorewall/modules (add ipt_owner)
modify /etc/shorewall/actions (register the actions)
I'd like to just include these files right in the upnpd.lrp file.
1) Since I'm a .lrp file, should the new files be added to
/usr/share/shorewall? The new files aren't really meant for user
consumption or manipulation
2) What's the best way to insure that upnpd.lrp "owns" these files
when the user does a backup of either shorewall or upnpd? It
would be evil for me to modify any of shorewalls files or package
config excludes?
Paul
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
