On 27 March 2016 at 08:52, Dave Love <d.love(a)liverpool.ac.uk> wrote:
Jason L Tibbitts III <tibbs-6Fsk2Ie8wHGVc3sceRu5cw(a)public.gmane.org>
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 scl stuff needs to be
installed initially, e.g. in copr root parameters, if you're going to
build scl packages at some stage.
(I don't understand why software collections aren't allowed so that more
packages could be contributed.)
You are running into one of the issues about why they weren't allowed
in base Fedora. This isn't the only macro problem that has come up and
while they each get eventually dealt with by the SCL guys.. it is a
whack-a-mole game...
> DL> Will the scl bug mentioned not be fixed?
>
> That would be up to whoever maintains the SCL macros.
Of course. I was thinking in terms of (lack of?) response to a bug
report which might get someone to look to it.
_______________________________________________
epel-devel mailing list
epel-devel(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject...
--
Stephen J Smoogen.