On Thu, Oct 17, 2019 at 7:48 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
On Thu, Oct 17, 2019 at 7:42 AM Stephen Gallagher <sgallagh(a)redhat.com> wrote:
>
> Similarly, the example of "build on Rawhide, run anywhere" was
> backwards. I should have said "build on oldest supported Fedora, carry
> through".
Modules currently fail at this because they have a platform
dependency.
I meant to address that in an earlier email when I saw you mention
that. It was wrong then, too.
Most modules *specify* a platform dependency, but they *do not have to*.
Take a look at the maven module, for example:
https://src.fedoraproject.org/modules/maven/blob/3.5/f/maven.yaml
You will notice that it specifies F29 as a build requirement but
specifies '[ ]' for the platform: this means "Build it on F29, run it
anywhere".
And we could *easily* permit it for non-modular packages
if we actually wanted it. I think we've generally said we don't want
to maintain content that can't be built for current releases, so this
is problematic.
We could permit it, sure. Modularity has facilities for implementing
it already, whereas non-modular would need to grow new rules for the
Message Tagging Service or do a lot of manual tagging.
Also, if we did this, we should drop the DistTag, because it
confuses
people otherwise.
Could you explain that?