https://bugzilla.redhat.com/show_bug.cgi?id=498390 --- Comment #53 from Petr Pisar <ppisar@xxxxxxxxxx> --- (In reply to Petr Pisar from comment #52) > TODO: I have no idea how the .lock files are used. But if they are used for > write-locking, then it will not work if /usr is a readonly file system. In > that case they should be placed into /var or /run with tmpfiles.d technique > <https://fedoraproject.org/wiki/Packaging:Tmpfiles.d> and rakudo should have > be patched accordingly. I thing this a good candidate for a bug report to > upstream. > docs/module_management.md reads: When we install a distribution, we do the following: 1. Create the `repo.lock` file; if it already exists, fail. So maybe the repo.lock file should not exist at all in rakudo binary package. And maybe it's irrelevant for read-only /usr because user won't be able to install any Perl6 distribution at all. What worries me is precomp directory that will need to regenerate its content when updating a distribution that is used by an already installed distribution. If it won't be be possible to prebuild in Koji, there will need to be some postscript in each RPM package or I don't know. -- You are receiving this mail because: You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx