We are looking at making a new platform stream for ELN builds (called, unimaginatively, eln).
eln
In order to avoid inconsistencies, we don't want platform: [] to expand to include eln. Packagers would have to manually include platform: [ eln ] as a separate entry in the [Build]Requires section of the modulemd.
platform: []
platform: [ eln ]
[Build]Requires
Can you please add a configuration option to exclude certain named streams from expansion?
Can we bump up the priority on this request please? This is a blocker to supporting modules in Fedora ELN.
I think the best way to approach this would be adding additional metadata to the platform module definition, maybe in the xmd section, something like invisible: true or somesuch.
platform
xmd
invisible: true
Such modules would not get pulled into stream expansion but could still be requested explicitly.
How complex do we expect these exclusions to get?
I'm not sure what you're asking here. Can you explain?
How often do we expect to add platforms that need to be excluded?
Do we expect to need to shift platforms from excluded to not?
Will we eventually need a syntax for "build on all the relevant eln platforms"?
I'm wondering if it would be better to hide platforms individually, as Petr suggests, or to have some sort of system config for what [] should expand to.
[]
I'm also wondering if this is going to eventually balloon into more complex platform syntax.
Thanks for the clarification.
I have no expectation that we'll need to add any others besides platform:eln at this time. Adding such a platform will be an incredibly rare event, should it occur again.
platform:eln
Not at this time, but it's theoretically possible.
ELN is a single platform that tracks Rawhide. This should never change.
I'm wondering if it would be better to hide platforms individually, as Petr suggests, or to have some sort of system config for what [] should expand to. I'm also wondering if this is going to eventually balloon into more complex platform syntax.
Commit e5d0b39 fixes this issue
Commit 669318f fixes this issue
Login to comment on this ticket.