On 04/11/2016 08:30 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> I would shoot for idea where the bla.macros would just sit in git and
>> the packages would specify as sources the macros ie.:
>> Source99: https://github.com/rpm/rpm-macros/archive/python.macros
Yes. This is about what I had in mind
On Mon, Apr 11, 2016 at 2:30 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> This moves those macros under the maintenance of the rpm team.
> I guess this could work for a few projects, let's say perl and python,
> but I don't see how this can scale (to perl, python, java, js, lisp,
Orion Poplawski píše v Po 11. 04. 2016 v 09:11 -0600:
> On 04/11/2016 07:46 AM, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > Hi,
> >
> > On Fri, Apr 01, 2016 at 01:45:15PM +0200, Tomas Chvatal wrote:
> > >
> > > Atm most of the macros are stored together with the packages they
> > > are
> > >
Hi,
On Fri, Apr 01, 2016 at 01:45:15PM +0200, Tomas Chvatal wrote:
> Atm most of the macros are stored together with the packages they are
> used for (kde macros in kde, systemd in systemd, python in python, etc
> etc).
...and that sounds just right. Macros should evolve along with their