On Sun, Oct 28, 2007 at 05:21:08PM +0000, Andrew Suffield wrote: > On Mon, Oct 22, 2007 at 09:24:16AM -0400, Roberto C. S?nchez wrote: > > On Fri, Oct 12, 2007 at 07:18:13AM +0100, Andrew Suffield wrote: > > > > > > The best approach is usually to maintain the Debian package > > > independently, and then regularly copy the debian/ directory back into > > > the upstream tree - so that part of the tree is actually downstream > > > from the Debian package itself. It sounds a little weird, but it's > > > invariably simpler than any of the other ways, and gets the job done. > > > > > > > OK. I will be doing this starting now. That is, I will remove the > > debian/ dierctory from the 3.4 branch (as that branch will see no > > further releases packaged for Debian) and then start copying the > > debian/directory into 4.0 and trunk. > > For some reason, the debian/ directory is missing from > shorewall-common in the 4.0.6-RC1 tarball - it's present in the other > components. Bug in the release building script?
Also, this bit in debian/rules: export V=`cat install.sh | grep "^VERSION=" | head -n 1 | cut -f 2 -d "="` VMAJOR:=$(shell echo $(V) |cut -f 1 -d .) VMINOR:=$(shell echo $(V) |cut -f 2 -d .) VPATCH:=$(shell echo $(V) |cut -f 3 -d .) NEXTPATCH:=$(shell expr $(VPATCH) + 1) breaks when the version number ends in -RC1. And you win the "useless use of cat" award. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
