[csw-devel] SF.net SVN: gar:[21544] csw/mgar/pkg/tiff/trunk

[Peter FELECAN]

Laurent Blume <laurent at opencsw.org> writes:

> On 2013-07-23 5:09 PM, Peter FELECAN wrote:
>> lblume at users.sourceforge.net writes:
>> 
>>> +GARCOMPILER = GCC4
>> 
>> saying GARCOMPILER = GNU is just more generic
>
> Fair enough. To be honest, I don't quite understand the rationale behind
> it. In fact, I'm becoming convinced a generic compiler choice is just
> not what I want.
> A decent default (when no GARCOMPILER is given) is good, but when I set
> one, I want to know exactly which one I meant and tested, without having
> to remember 2 years from now what the generic was at the time. And when
> GCC5 becomes the default anyway, every recipe with GNU in it will have
> to be carefully reviewd, and packages rebuilt when ABI are incompatible.
> So why bother?

The reverse is true also. GCC doesn't change ABI's so often, quite
rarely. If you look in our recipes, what I proposed is the more frequent
form and it a good thing like that.

>>> +CONFIGURE_ARGS += --enable-maintainer-mode
>> 
>> why do you enable that?
>> 
>
> Because it seems fitting, as I'm maintaining the package :-)
> I've not checked in details what it does, but it's in the howto-release,
> it doesn't break anything, so looks good to me.

Are you maintaining the upstream project? From my point of view you're
packaging it, which is quite different. If you look at what means
"maintainer mode" in GNU standards you'll be quite surprised. This is
why I think that such an option is to be activated only exceptionally in
our situation.
-- 
Peter