Dne 02. 12. 22 v 14:00 Vít Ondruch napsal(a):
Dne 02. 12. 22 v 13:11 Mamoru TASAKA napsal(a):Vít Ondruch wrote on 2022/12/02 21:02:Dne 21. 10. 22 v 15:33 Vít Ondruch napsal(a):Dne 21. 10. 22 v 13:56 Mamoru TASAKA napsal(a):* 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.But it could be better, if the date is always first: 3.2.0~20220916git6ad6994457 3.2.0~20221012git70bc8cc6c 3.2.0~20221015preview1 3.2.0~20221101preview1^git4b1504ae0a But I am not sure this is not overcomplicated. So any other scheme which would work? 😇Just use tilde + date + some other git / preview / or random string, I think this is easy usage.Ah, right. I was overthinking this. If the date is there, change from `preview` back to `git` doesn't really matter. Will look at it.
So this is result of my tinkering: https://src.fedoraproject.org/rpms/ruby/c/fa665a95d97dc6da8175c682681e66a2e161a845?branch=private-ruby-3.2 https://koji.fedoraproject.org/koji/taskinfo?taskID=94834602The release still must be higher then last Ruby release. It should actually be higher then the release of overlapping gems such as rubygem-{rdoc,json}. Maybe I should bump it to -300?
Vít
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
