Aleksandra Fedorova wrote:
> I see that Mikolaj has a vision how it supposed to work. And I think he
> spent quite some time designing the workflow which would fit this vision,
> thus it is worth to listen to it with an open mind.
>
> @Mikolaj, can you document the setup for java toolchain somewhere other
> than a mailing list? Buildroot modules, defaults streams, what Java
> packager should and shouldn't use... Probably one of those outdated wiki
> pages can be updated for that.
Buildroot-only modules? Stuff Java packagers shouldn't use? Why should we
let one individual packager hold the entire Java ecosystem on Fedora hostage
with such antisocial diktats?
I stand by my position that buildroot-only content of any kind (buildroot-
only packages, buildroot-only modules, packages filtered from modules, etc.)
should just not be allowed in Fedora, ever. (And where it has already
slipped through, it needs to be made user-installable (and available for all
other packages) as soon as possible.) This is not even directly related to
Modularity, Modularity just happens to be the way this anti-feature was
implemented.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
