On Fri, Apr 08, 2011 at 11:18:50PM +0000, Karl Berry wrote: > +dist-hook: > + tar -C $(srcdir) -c -f - --exclude CVS tp | tar -C $(distdir) -x -f - > > Why do we want tp in the dist at this point? As far as I understand > from Patrice, it's not ready. And when it is ready, it will be merged > into the configure stuff in the standard way.
I am still unsure how easy it is. I did a little bit of investigations when I started tp/ on integrating a perl module (which is what tp/ basically is) with autoconf/automake but I found nothing obvious. Also if tp/ is to be distributed separately too (which I think would be nice) there should also certainly be some adjustments. > And yes, there are lots and lots of tests for make distcheck to go > through. I don't know if it's feasible or desirable to omit the > lengthiest ones. I'm sure I will want to figure that out when we get to > the glorious day of actually making a new distribution :). Right now those are the tests of texi2html that are run, not those of tp/. Current tp tests are much better focused, and, in addition, tp is a bit faster. Parser, Info and Plaintext tests are already done, and they don't take too much time, in my opinion. In any case, I fully agree that current texi2html tests are much too long, I even think that they almost become detrimental for the developpement... -- Pat
