Le mercredi 20 octobre 2010, à 23:22 +0200, Vincent Untz a écrit :

Le mercredi 20 octobre 2010, à 23:14 +0200, Marcus Rueckert a écrit :

...

On 2010-10-20 17:01:17 -0300, Cristian Rodríguez wrote:

...

I see an increasing amount of stuff using automake's new AM_SILENT_RULES feature, remember to use --disable-silent-rules or "make V=1" when you submit the package for build.

This feature breaks current build checks that rely on analizing the output of the build log.

Thanks for flying with openSUSE :-)

maybe we should add it to %configure ?

Probably better to just define V=1 (I can imagine it could break some configure scripts).

Let me rephrase to be clear: I can imagine --disable-silent-rules could break some configure scripts. Sorry for the noise :-) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Hello, On Wed, 20 Oct 2010, Cristian Rodríguez wrote:

El 20/10/10 18:28, Vincent Untz escribió:

...

Let me rephrase to be clear: I can imagine --disable-silent-rules could break some configure scripts.

Probably, the usual autotools joy :|

In comparison to the alternatives, yeah, probably "joy" ...: cmake, qmake, etc. pp. are more joyful? In my experience, autotools is still the easiest to debug, patch or "hack" BY FAR of all those tools. And some things (needed for packaging, not neccessarily as an author!) are not possible with e.g. cmake (or I haven't found _anything_[0]), that are more or less easily doable with autotools. And be it patching the actual "./configure"-script or Makefile.in with patch, sed/perl or whatever. One of the big pros for autotools is IMO that it's "package- contained"[2] and written in a well known "language" (m4/sh/make). No need to provide a certain set of certain versions of files "in system" for it to work. cmake and qmake though (AFAIK) need certain stuff "in system" for them to work. I can tell. I use _current_ software on a 11 year old install[1]. Almost all ./configure just work as unpacked (as long the dependencies are provided). Few need a little massaging (via patch/sed/perl/...). Everything else than autotools (and maybe imake) is always a real PITA, as it needs cmake $brandnew, or qmake $betafoo or bjam $svnversion or "why-dont-you-shoot-me-already == version 666" ... [Disclaimer: all that "version" stuff is meant exemplarily] But, of course: AHS, ASS. Some more, some less. In my experience autotools is the least sucky of the bunch by far. YMMV. -dnh, donning the asbestos suit, just in case [0] and I'm very good at finding stuff, ask e.g. Philipp ;) [1] an ex-6.2, dubbed "Hallerlix", not by me originally ;) [2] i.e. self-contained on a per-package basis, only when you patch the .in or .ac and have to regenerate stuff, or some stuff is missing you run into possible version conflicts (e.g. your autoconf being too old). -- == Re: Exchange's mailbox format == I hope that's not UI -- but the proper term is a "Jet database", accessed through the "Jet engine". A fitting name, considering that it sucks and blows. -- Felix -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org