Le mercredi 07 mars 2018 à 16:35 +0100, Nicolas Mailhot a écrit :
> Le mercredi 07 mars 2018 à 16:02 +0100, Jan Chaloupka a écrit :
>
> Hi,
>
> > Nicolas, can you more elaborate on that? I don't see any more reason
> > why we should block folks from relying on the new macros.
>
> IMHO they're so
Hi Athos,
hope everything is fine and you have better things to do than spending
much time updating the Go spec files :)
Anything you need and/or anything that could help you to minimize your
packaging time, please, let us know :).
On 03/04/2018 08:20 PM, Nicolas Mailhot wrote:
Le samedi
On 02/27/2018 07:22 PM, Nicolas Mailhot wrote:
Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit :
How do we test this? I installedtho go-srpm-macros from Rawhide but it
doesn't seem to have the required macros?
Yes in rawhide go-compilers and go-srpm-macros are in an inte
Le samedi 03 mars 2018 à 11:47 -0300, Athos Ribeiro a écrit :
>
> Are there any intentions to push the macros into f28? I really liked
> the
> improvements in the spec file sizes, but porting too many packages now
> and keep them updated in both f28 and rawhide (making the branches
> completely di
On Tue, Feb 27, 2018 at 07:22:42PM +0100, Nicolas Mailhot wrote:
> Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit :
> >
> >
> > How do we test this? I installedtho go-srpm-macros from Rawhide but it
> > doesn't seem to have the required macros?
>
> Yes in rawhide go-compile
Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit :
>
>
> How do we test this? I installedtho go-srpm-macros from Rawhide but it
> doesn't seem to have the required macros?
Yes in rawhide go-compilers and go-srpm-macros are in an intermediary
not fully tested/integrated state.
