[EPEL-devel] Re: using epel-rpm-macros

2016-03-25 Thread Jason L Tibbitts III
> "DL" == Dave Love writes: DL> In preparing the recipe with the minimal spec to demonstrate, I DL> realized it's because it doesn't work if you have scl build stuff DL> installed. Yep, it explicitly gets out of the way if the SCL stuff is there. This is to avoid bugs in the SCL macros. DL

[EPEL-devel] Re: using epel-rpm-macros

2016-03-25 Thread Jason L Tibbitts III
> "SJS" == Stephen John Smoogen writes: SJS> What bug? Sorry we really need to see some actual output and SJS> problems here to have an idea of what we are trying to tackle. I think he's referring to the fact that the SCL macros break if you try to do too much with other macros. I could pro

[EPEL-devel] Re: using epel-rpm-macros

2016-03-25 Thread Stephen John Smoogen
On 25 March 2016 at 10:46, Dave Love wrote: > Jason L Tibbitts III writes: > >> And I just pulled two random package with EL6 branches, changed %doc to >> %license in the appropriate places, and built them in mock. Everything >> came out as expected (no build failures, and the license files are

[EPEL-devel] Re: using epel-rpm-macros

2016-03-25 Thread Dave Love
Jason L Tibbitts III writes: > And I just pulled two random package with EL6 branches, changed %doc to > %license in the appropriate places, and built them in mock. Everything > came out as expected (no build failures, and the license files are in > with the rest of the documentation). > > So I