You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this time, ghc is not currently in use in ELN Extras, but it certainly could be, as it is in EPEL. Can and should we have an eln branch of epel-rpm-macros and add it to the eln default buildroot?
That depends on whether the meaning of ELN Extras is indeed future EPEL. If so, I would say we should have that branch.
add it to the eln default buildroot
That's trickier. It should not be in the eln buildroot, only in the eln extras buildroot. But if the 2 buidlroots are not separated, that cannot be done.
With ELN Extras rebootstrapped, I'm seeing more failures due to a lack of certain macros. If we can't separate ELN Extras from ELN entirely, then we probably need at least an eln-extras build tag and target with an ELN build of epel-rpm-macros included by default.
Hello,
after looking at https://src.fedoraproject.org/rpms/redhat-rpm-config/c/f7d9eeb359404d01e388c21b1697ad24aeddcea9?branch=rawhide I am wondering about one thing:
What if we need ghc-srpm-macros installed in the ELN Extras buildroot, but at the same time, it is unwanted in ELN?
If ELN Extras was EPEL, we would add the dependency to epel-rpm-macros. However, it is not.
Is there a package that is installed by default in ELN Extras only? Should we create it? Or is this use case to niche?
The text was updated successfully, but these errors were encountered: