standards
> and practices for Fedora"
> <packag...@lists.fedoraproject.org>
> Sent: Monday, February 5, 2018 3:27:01 PM
> Subject: Re: [Fedora-packaging] Re: Re: Proposed Fedora packaging
> guideline: More Go packaging
>
>
>
> - Mail original -
> De:
- Mail original -
De: "Jakub Cajka"
> Our as Fedora or yours company/org? I believe that your contribution of those
> in to Fedora will be much
> appreciated.
Our was meaning the set of specs we are preparing for inclusion. Can't really
share them before the macros they depend on
- Original Message -
> From: "nicolas mailhot"
> To: gol...@lists.fedoraproject.org
> Cc: "Development discussions related to Fedora"
> , "Discussion of RPM packaging
> standards and practices for Fedora"
On Tue, Jan 23, 2018 at 9:00 AM, wrote:
>
>
> - Mail original -
> De: "Neal Gompa"
>
>> As long as I can do Obsoletes/Provides for the old name for the devel,
>> unit-test,
>
> BTW is anyone using the unit-test packages? Right now I do not generate them,
> I
- Mail original -
De: "Neal Gompa"
> As long as I can do Obsoletes/Provides for the old name for the devel,
> unit-test,
BTW is anyone using the unit-test packages? Right now I do not generate them, I
don't need them, and making them work with autodeps would be hairy (deploying
- Mail original -
De: "Neal Gompa"
>> 2. if your concern is that the *forge* macros are defective somewhere I'd
>> be curious where as you'd be the
>> first to report an actual technical problem. I've used them intensively in
>> rawhide and el7 with many different
>>rpm tools and
On Tue, Jan 23, 2018 at 5:45 AM, wrote:
>
>
> - Mail original -
> De: "Neal Gompa"
>
>>On Mon, Jan 22, 2018 at 8:33 AM, Dridi Boukelmoune
>>
I really do like this. There are only two issues I have with it:
1. This seems to mandate that all