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

On 27 March 2016 at 08:52, Dave Love wrote: > > > Jason L Tibbitts III > writes: > >> If you have a build dependency on the SCL tools then you're obviously >> not building for EPEL, > > Well, I'm building for people running

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

On 27 Mar 2016 15:58, "Dave Johansen" wrote: > > On Sun, Mar 27, 2016 at 7:52 AM, Dave Love wrote: >> >> >> >> Jason L Tibbitts III >> writes: >> >> > If you have a build dependency on the SCL tools

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

On Sun, Mar 27, 2016 at 7:52 AM, Dave Love wrote: > > > Jason L Tibbitts III > writes: > > > If you have a build dependency on the SCL tools then you're obviously > > not building for EPEL, > > Well, I'm building for people

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

Jason L Tibbitts III writes: > If you have a build dependency on the SCL tools then you're obviously > not building for EPEL, Well, I'm building for people running EPEL, and I didn't see this isn't with packages that depend on anything scl. The

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

> "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

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

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 unfortunately have no idea what might be

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

> "DL" == Dave Love writes: DL> How is the epel-rpm-macros package supposed to work? I have DL> epel-rpm-macros-6-4 installed, which is up-to-date against DL> epel-testing, and is supposed to make %license work like %doc but DL> doesn't seem to have any effect.