On Thu, Feb 7, 2019 at 2:13 AM Adam Samalik <asamalik(a)redhat.com> wrote:
2) Fedora infra builds of standalone packages — modular content is
currently invisible to standalone package builds. That said, the Modularity Team is
actively working on making that possible. You might have heard about "Ursa
Major" which is a funny name for a solution that injects default module streams into
the traditional buildroot. Alternatives have been also discussed in the past few weeks.
But please understand this the reason it doesn't work at this moment is not the
design, but rather the work still being in progress. And before that's done, we do not
allow packages used as build dependencies to be completely moved to a default module
before we fix this — so nothing should break for you.
A couple of days ago, Mikolaj Izdebski announced on this mailing list,
in a thread entitled "Orphaned some Java packages" that 259 packages
are being converted into modules. So none of those are used as build
dependencies? I can tell you for sure that one of them SHOULD be used
as a build dependency:
https://bugzilla.redhat.com/show_bug.cgi?id=1599015
What should happen is that coq has antlr4 as a build dependency, uses
it to generate some python code, then depends on the antlr4 python3
runtime. Since that isn't possible at the moment, I've been forced
into the stupid, wrong workaround of (a) using upstream's generated
python code, since our antlr4 package is incapable of regenerating it,
and (b) bundling the antlr4 python3 runtime with coq, since it is not
available from Fedora in any package. Now what is going to happen?
If antlr4 becomes a module, how will this situation be resolved?
I am very concerned that the coq situation is going from bad to worse.
Give me some hope.
--
Jerry James
http://www.jamezone.org/