Le lundi 22 octobre 2018 à 10:00 +0200, Nicolas Mailhot a écrit :
> Le lundi 22 octobre 2018 à 00:31 +0200, Robert-André Mauchin a écrit :
> > Yeah all "gosetup -q" (which is gofed default) are broken because of
> > your commit:
> 
> Well I know no such a thing, there was never any gosetup macro in the
> macro set, and I think I told you a year ago I would not define a
> gosetup macro just to avoid typing forgesetup, unless it actually
> added
> some processing over the forgesetup macro. That would obfuscate specs
> for no good reason and increase gratuituously the maintenance surface
> (as we see *now*).
> 
> And I doubt -q is your problem, since (*precisely for backwards
> compatible reasons) it is still accepted by forgesetup (even though
> it's
> ignored, because it’s the default behaviour now).
> 
> Oh, I see, I forgot to add a phantom -q to forgeautosetup as it
> already
> was already its default behaviour. So you're forcing somewhere a -q
> that
> I don't think was ever needed. I will add the -q to the macro
> definition
> if that makes you feel better.
>
> So, no biggie. Easy to fix. That's why such changes hit -devel before
> anyone dreams of queuing them to stable.

And it's here:

https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/45



-- 
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to