--- Tom Eastep <[EMAIL PROTECTED]> wrote:
> So you are in favor of releasing all packages with
> each Shorewall release?
At first I would say so (for simplicity) but then
again it really doesn't matter just as long as I know
that different versions can be released and are
intercompatible.
> The advantage of releasing the packages separately
> on
> their own schedule is that we end up with fewer
> total
> packages to support. The downside is the
> never-ending
> confusion that users will have about what works with
> what.
That's what I am considering since I'm proposing
shorewall ebuilds for the Gentoo portage packaging
system. The way ebuilds can be scripted is different
if we know that the shorewall-* versions will always
have to be the same (in this case only a single
shorewall ebuild would be necessary with just a
parameter to pull in a specific compiler). However, if
shorewall-* versions will differ and be interoperable
then separate ebuilds are more appropriate.
I guess I'll consider the "separate ebuild" route just
to be on the safe side.
____________________________________________________________________________________
Got a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
