2008/11/17 Charles Lepple <[EMAIL PROTECTED]>: > On Sun, Nov 16, 2008 at 10:05 PM, Charles Lepple <[EMAIL PROTECTED]> wrote: >> On Sun, Nov 16, 2008 at 5:44 PM, Arnaud Quette <[EMAIL PROTECTED]> wrote: >>> 2008/11/16 Arjen de Korte <[EMAIL PROTECTED]>: >>>> Citeren Charles Lepple <[EMAIL PROTECTED]>: >>>> >>>>> I haven't looked into this much, but do we want to remove some of the >>>>> generated files from SVN, and have the build process generate them >>>>> every time? This would ensure that they are always up-to-date. >>>> >>>> I think we should, this is as far as I can see the whole purpose of >>>> this exercise. >>> >>> I wanted to do so, but refrained myself because of the Perl depends... >>> that's why I've put it in the dist target. >> >> Hmm, I'm not sure the tools directory is getting built. >> >> However, if someone is building from SVN, they need auto*, which means >> they need Perl. > > Ah, we are running 'make distcheck(-light)' in Buildbot, versus 'make dist'. > > Still, I think we should make this part of the normal build procedure > (or at least 'make distcheck'), but we can use 'make dist' to > distribute the USB files on the off-chance that someone doesn't have > Perl installed when they build from a tarball. (We aren't depending on > a specific version of Perl, so it's not an outrageous dependency.) > > Otherwise, nobody will ever test this.
well, the aim is not to test this, but to have up to date USB data upon dist release. but, you're right about the perl deps, and I'm fine with generating this along with autoreconf or distcheck or whatever suits you. cheers, Arnaud -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
