Hi all,

I’ve had some discussion with Jonathan Wright elsewhere about the topic of this 
message, but wanted to verify my understanding is correct before I embark on 
it, and thought I’d do so on list.

singularity-ce is currently packaged at v4.0.3 in Fedora Rawhide, and v.3.11.5 
elsewhere (Fedora releases and EPEL).

We want to make a v4 available to EPEL users, as many would be interested in 
it, but I wouldn’t consider it a compatible update because there are some CLI 
changes, and small behaviour changes.

My understanding is that in order to provide a 4.x in EPEL, without any 
incompatible update happening for users:

1) I create a new package, singularity-ce4, to package the 4.x version. In 
rawhide, this will be the same as the singularity-ce package currently in 
rawhide, but needs new package review etc.

2) For rawhide / upcoming f40 *only*, the new singularity-ce4 package will 
provide/obsolete singularity-ce as it is the same thing … and singularity-ce 
can be retired in rawhide.

3) When singularity-ce4 is added to EPEL it will *not* provide/obsolete 
singularity-ce, but a message can be added to %post to inform people about the 
availability of v4.

At some point in the future, if 3.x is no longer maintainable for good reason, 
then the incompatible update procedure can be pursued to make singularity-ce4 
provide/obsolete singularity-ce in EPEL 7/8/9 - and singularity-ce is fully 
retired. EPEL 10 will only get singularity-ce4.

Apologies for the multiple complex queries lately. I really appreciate your 
guidance!

Dave Trudgian
--
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to