Re: [ELN] Creating a process for ELN-specific changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 14, 2021 at 06:38:33PM +0200, Miro Hrončok wrote:
> I wouldn't say so. I'd say "package both versions as separate
> non-modular RPM packages with unique names" is the general answer
> when different versions of the package are desired.
> 
> However, the problem here is different. We don't want 2 different
> versions packaged in Rawhide AND 2 different versions packaged in
> ELN. We want to allow package versions in ELN and Rawhide to be
> different.

This is exactly a case that modularity is supposed to handle. Two different
versions packaged only one time each, built for both targets automatically,
with one the default on target A and the other the default on target B,
output, but with either version selectable in either target.


-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux