On Sat, Jun 21, 2014, Ralph Corderoy wrote:
mom's PDF_IMAGE macro could remain a float with lots of bells and
whistles to the user but make use of an underlying macro-set-agnostic
macro to do the PDF inclusion as Tadziu suggested; provide a
bare-bones PDF image includer à la PSPIC instead.
On Sat, Jun 21, 2014, Ingo Schwarze wrote:
It is certainly nice to see when upstream groff development makes
progress. However, i would consider it common practice for
upstream committers to test the build before committing, rather
than relying on downstream consumers to catch trivial build
It is certainly nice to see when upstream groff development makes
progress. However, i would consider it common practice for
upstream committers to test the build before committing, rather
than relying on downstream consumers to catch trivial build system
bugs...
Ingo's right. We need
This is probably a good time for me to pop this question which I have had
for a while: Don't we have a formal unit-test/review cycle around the
commits we make into the code base? Also do we have any test suites around
major packages that can quickly sanitize our checkins? Or an automated
build
Don't we have a formal unit-test/review cycle around the commits we
make into the code base?
Not really. Given the small amount of committers, it wasn't
necessary. Bernd is working on his sub-projects within the
repository, and this is just fine. The same for Peter and Deri. I
was handling
