Hi Steffen,
> I have your message also in my queue but it will take quite some
> time until i will be able to use your test.
> ..I agree with Betrand: it would be better to understand the code
> paths as such.
I definitely agree, although as I said to Bertrand, I think the first goal
should be t
Hi Bertrand,
On Sep 22, 2014, at 2:05 AM, Bertrand Garrigues
wrote:
> Are you thinking of unit tests, using a test framework for C++, or more
> global tests (using for example shell script) ?
I was thinking of system-level tests, at least initially. For example, the
grohtml postprocessor oper
Hi Ingo,
On Mon, Sep 22 2014 at 10:38:40 PM, Ingo Schwarze wrote:
> You might also wish to add a sentence like the following to
> INSTALL.REPO, right after "1. Initial build", before "First invoke
> the bootstrap script:"
>
> On operating systems supporting concurrent installation of multiple
>
Hi Bernd,
On Mon, Sep 22 2014 at 08:52:55 PM, "Bernd Warken"
wrote:
> ### ./test-suite.log:
>
> FAIL: contrib/gdiffmk/tests/gdiffmk_tests.sh
>
> /opt/development/groff/git/automake/patched/build/../contrib/gdiffmk/tests/runtests.sh:
> 50:
> /opt/development/groff/git/automake/patched/build/../co
> So this code in ./bootstrap is suboptimal:
>
> check_exists() {
> ($1 --version /dev/null 2>&1
>
> That deliberately hides the error message from the user and displays
> a bogus message instead, so you might wish to refrain from hiding
> stderr.
... given that `bootstrap' is a ready-to-
Hi Ulrich,
On Mon, Sep 22 2014 at 05:09:31 PM, Ulrich Lauther
wrote:
> To make this work on my ubuntu 12.04 LTS „Precise Pangolin“ system I
> had to apt-get install autoconf automake libtool texinfo bison flex
>
> and then to install automake 1.12.2 from source, as the version 1.11.3
> that came
Hi Bertrand,
Bertrand Garrigues wrote on Sun, Sep 21, 2014 at 09:14:27PM +0200:
> With commit a88127a4fecb307f26f2e217213d4a90e300d220 the automake2
> branch is now ready for more testing from other members of the list.
Here are some experiences and suggestions:
$ ./bootstrap 2>&1
./bootst
On 22-Sep-2014 19:55:37 Doug McIlroy wrote:
> I had reason today to run groff on an eqn|troff -ms input file
> dated Aug 2 1979. It took a 1-character change (missing space
> in .in0) to make it work!
>
> Doug
Congratulations Doug! (As much for having that file available
in the first place, as fo
I had reason today to run groff on an eqn|troff -ms input file
dated Aug 2 1979. It took a 1-character change (missing space
in .in0) to make it work!
Doug
> Von: "Bertrand Garrigues"
> > 1) make check
> - Could you please send me the content of build/contrib/gdiffmk/tests ?
See the added archive test.tgz.
#
> - What happens if you call manually gdiffmk_tests.sh ? For example like
> this:
$ abs_top_builddir=/opt/development/groff/git/auto
Hi Peter,
Peter Schaffter wrote on Sun, Sep 21, 2014 at 09:39:17PM -0400:
> Sorry not to get back on this right away. I've been away for a
> couple of days--work and computer free!
No problem. Unless a software project will be abondoned soon,
a few days delay really don't matter.
> On Fri, Se
Hello Robert,
Robert Bocchino wrote:
|On Sep 21, 2014, at 2:25 PM, Bertrand Garrigues wrote:
|> I am not qualified to review your patch because I haven't studied
|> grohtml's code, but I've tested it on the few .html files that are built
|> by default in the 'doc' directory from pic.ms and w
On Mon, Sep 22, 2014 at 01:17:39AM +0200, Bernd Warken wrote:
>
> I would improve your install commands a bit into:
>
> test -d old && rm -rf old
> test -d groff && mv groff old
> git clone git://git.savannah.gnu.org/groff.git
> cd groff
> git checkout automake2
> ./bootstrap
> mkdir build
> cd
Robert,
On Mon, Sep 22 2014 at 01:56:10 AM, Robert Bocchino wrote:
> I'm thinking it might be a good idea to start developing a test suite
> for grohtml. That would (1) document what grohtml is supposed to do,
> including identifying current known bugs, and (2) provide a systematic
> way to veri
Hello Bernd,
Thanks for testing!
On Mon, Sep 22 2014 at 01:23:56 AM, "Bernd Warken"
wrote:
>> Von: "Bertrand Garrigues"
>> Then you can check in the TESTS file for the other targets. Please note
>> that compared to the current build system:
>> - There are 2 new targets, 'make check' and 'ma
> Strictly speaking, in PostScript also each page can be a
> different size (though there is nothing built-in to groff to
> arrange this).
This is correct, but because it is not clear what it would mean
to include a multi-page document as a graphic, let's simply
agree it should not be done. For
16 matches
Mail list logo
