Re: [Viking-devel] Imminent Viking 1.4 Release
Robert Norris rw_nor...@hotmail.com writes: The NetBSD nan patch is integrated; thanks again (I'm sure I sent this in a long time ago :-). Not sure when ( almost before my time! ) Sorry, I am confused. It is in my local tree as a patch that I rebase, and hence in the tarball I generated. make distcheck fails because it doesn't carry the CPPFLAGS from the invocation of configure. (Not sure if that's legimately a bug, and I don't expect any of you to fix it, but thought I'd mention it.) Interesting observation - my CPPFLAGS '-O0 -g' to make debugging easier. This is carried over into make distcheck, on a Debian Unstable AMD64 make --version GNU make 3.86 Hmm. I'll have to check that harder. Hmm, I think I have may have (indirectly) removed help from tarball in trying to simplify the build dependencies. In principal *only* a 'full' build generates the help PDF from the DocBook XML help - this is more of a Windows build simplification/avoidance, especially since the help Makefile relies on ../gnome-doc-utils.make' which may not be available - how to do conditional 'includes' in a Makefile anyone?). Unfortunately I now see that some of the 'src' depends on the XML if you have 'xsltproc' available on your system, as then documenters.h is generated by processing the xml file. Personally I find automake Makefile.am a horrid interwoven web of implicit Macros in an obscure language I don't use anywhere else - so it's hard to know what's right! I'd like to put the XML help in the source generation, but not actually use it in a build but how (given the Makefile has an include statement) ? I'm not sure what to do, but I wonder if making the xsltproc part of the build non-optional would help. gtk doc tools and xsltproc are pretty normal on any machine beefy enough to run viking, I would think. I think gnome-doc-utils.make is available in the tarball. Or are you worried about Windows users building from source when they don't have the doc tarballs? I wonder if it's easy to omit the build rules, but to leave the additions to the distfiles. pgpy8DfhuXhAk.pgp Description: PGP signature -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Imminent Viking 1.4 Release
The NetBSD nan patch is integrated; thanks again (I'm sure I sent this in a long time ago :-). Not sure when ( almost before my time! ) My mistake, I think I closed the SF bug here (mostly due to being 'old' and see if anyone would notice): https://sourceforge.net/tracker/index.php?func=detailaid=1891884group_id=83870atid=570954 Sorry, I am confused. It is in my local tree as a patch that I rebase, and hence in the tarball I generated. Can you upload that to GitHub, repost the patch (or find a URL reference for it) please? Probably to late for inclusion in 1.4 Some ideas to on how to get it to work for different compilers/platforms: http://stackoverflow.com/questions/1923837/how-to-use-nan-and-inf-in-c http://tdistler.com/2011/03/24/how-to-define-nan-not-a-number-on-windows I'd like to put the XML help in the source generation, but not actually use it in a build but how (given the Makefile has an include statement) ? I'm not sure what to do, but I wonder if making the xsltproc part of the build non-optional would help. gtk doc tools and xsltproc are pretty normal on any machine beefy enough to run viking, I would think. Yes I've now given up in trying to avoid it. So now I've found Windows builds of xsltproc (and libxml2) so I have a complete Windows build using wine. I just need to resolve a nasty 'acquire' thread bug I introduced, but should have an updated git master very soon. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Imminent Viking 1.4 Release
Hi Greg, I think this is a recurrent question, each time a significant release is approaching. Deciding if a software like viking needs or not a release candidate cycle is an infinite debate. Last time, we discuss this topic, we decided to avoid release candidates. Instead, we release the version when it is ready and fix bugs in a following release. Last example is version 1.3.2.1. If you want to prepare a little, I think you can already fetch the current Git master branch. If you really prefer a pre-packaged tarball, I can send you the current version. But, as far as I know, a significant release related job is not job: writing the 1.4 part of file NEWS. But, perhaps Robert has another point of view. 2013/2/5 Greg Troxel g...@ir.bbn.com When it's almost ready, can you make a candidate release tarball, using the same mechanism as you will use for the release, and put it up as viking-1.4rc0.tar.gz? That way I can test the packaging path, and others can too, and we can fix anything small. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/ -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Imminent Viking 1.4 Release
I'm not one for RC candidates unless needed for some reason. Since we aim to release straight from the git master baseline (with just the version bump update), there are no merging various branching issues (i.e. this has already been done). I suppose the best practise is to announce our release intentions, which have happened in the past with I remember at least one 'string freeze' message. Previously I don't think between perhaps myself, Guilhem and (too a lesser extent) Greg, any one has shown an explicit interest in releases since we declared version 1.0, although various Distro's have picked up releases seemlessly - thank you. Some disto's offer 'continuous integration' anyway - I always hope that any individual git version (or at least after a merge stage) should be OK for release. Thus as far as I'm concerned posting some messages to this mailing list about the release intention is good enough. NB I had already responded to Greg, and (I believe) he's happy with the git release method Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. Date: Wed, 6 Feb 2013 22:23:11 +0100 Subject: Re: [Viking-devel] Imminent Viking 1.4 Release From: guilhem.bonnefi...@gmail.com To: g...@ir.bbn.com CC: rw_nor...@hotmail.com; viking-devel@lists.sourceforge.net Hi Greg, I think this is a recurrent question, each time a significant release is approaching. Deciding if a software like viking needs or not a release candidate cycle is an infinite debate. Last time, we discuss this topic, we decided to avoid release candidates. Instead, we release the version when it is ready and fix bugs in a following release. Last example is version 1.3.2.1. If you want to prepare a little, I think you can already fetch the current Git master branch. If you really prefer a pre-packaged tarball, I can send you the current version. But, as far as I know, a significant release related job is not job: writing the 1.4 part of file NEWS. But, perhaps Robert has another point of view. 2013/2/5 Greg Troxel g...@ir.bbn.commailto:g...@ir.bbn.com When it's almost ready, can you make a candidate release tarball, using the same mechanism as you will use for the release, and put it up as viking-1.4rc0.tar.gz? That way I can test the packaging path, and others can too, and we can fix anything small. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Viking-devel mailing list Viking-devel@lists.sourceforge.netmailto:Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/ -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.orgmailto:gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.commailto:guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.commailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
[Viking-devel] Imminent Viking 1.4 Release
Viking 1.4 is taking shape to be released next Monday February 11th 2013. Not only just source code, but a Windows Binary is expected to be produced too! Around 188 new/changed** text strings have been introduced which require translating.* I know this is short notice, but if any one can help out - please use the Translation facilities on Launchpad: http://translations.launchpad.net/viking/trunk * So sadly the German, Czech and Finnish translations are no longer 100% complete. **We did try to keep this to a minimum number of changes honest! Be Seeing You - Rob. If at first you don't succeed, then skydiving isn't for you. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
