Dne 21. 10. 22 v 13:56 Mamoru TASAKA napsal(a):
Vít Ondruch wrote on 2022/10/17 23:24:Hi again,Here is yet another version from Friday: https://koji.fedoraproject.org/koji/taskinfo?taskID=92978738Nothing really special from Ruby POV, but I have enabled out-of-source build, as was previously discussed here:https://src.fedoraproject.org/rpms/ruby/pull-request/120 https://src.fedoraproject.org/rpms/ruby/pull-request/122So while this should not have any influence on resulting package, it might come handy when somebody wants to clean the source tree and play with e.g. different configuration options or what not.VítThank you. By the way, do you have some plan to bring ruby 3.2 development rpm to f38 buildroot earlier than 2022 Christmas (say, around 2022/11/E)?
Short answer is no.Honestly, I don't trust Ruby upstream they will keep their ABI stable enough and I have never tried to ask what is their stance here. From my POV, with exception of the final release date, the development always appeared quite random. I remember several years the huge changes in their configuration scripts done just during the December, few days/week prior the release (which of course says nothing about ABI stability ...)
The reason I am asking here is that: * As I wrote above, ruby3.2 is to be released on 2022/12/25 (perhaps), usually we wait for this, and actually ruby mass rebuild usually begins around 2nd week of January? Then mass rebuild for whole Fedora packages (for F38) begins at 2023-01-18, so (as usual) the timing is very tight.
Oh, I have not checked the dates. This comes earlier and earlier :/ If it was even earlier, we could do our rebuild afterwards ;) I could ask Ben, what are his thoughts and why there are 3 weeks for mass rebuild followed with branching right away.
* Now rpm supports tilde, tilde is regarded as older than non-tilde version. So we can use, say, ruby-3.2.0~preview2-170.20221021gitabcdefg.fc38, for example,without "resetting" release number to 0.1.XXXX.Then we can set the release number of subpackages (such as rubygem-io-console) to (0.5.12-)170.gitabcdefg.fc38, so now we don't have to fight with release number,just we have to keep increasing this.
The release number was never priority for my local experiments. But the tilde is probably something to consider. Not sure what impact it will have on the work with the archive name etc. But it could help with the Copr rebuilds and what not. Thx for pointing this out. I'll try to take 2nd look.
Vít
* And perhaps on 2022/11/E, I guess ruby3.2 would almost stable. Regards, Mamoru _______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org 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/ruby-sig@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
