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=92978738
Nothing 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/122
So 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ít
Thank 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)?
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.
* 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.
* And perhaps on 2022/11/E, I guess ruby3.2 would almost stable.
Regards,
Mamoru
_______________________________________________
ruby-sig 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
