FS#25658 - [devtools] move .lock files generated by mkarchroot and makechrootpkg to /run or some other place
Attached to Project:
Arch Linux
Opened by Auguste Pop (Auguste) - Thursday, 18 August 2011, 22:21 GMT
Last edited by Kristian (klausenbusk) - Saturday, 03 June 2023, 18:04 GMT
Opened by Auguste Pop (Auguste) - Thursday, 18 August 2011, 22:21 GMT
Last edited by Kristian (klausenbusk) - Saturday, 03 June 2023, 18:04 GMT
|
Details
Description:
those .lock files do not have to be named after the directory and put alongside it. we may give a static name for every fd we use. Additional info: * package version(s) git HEAD * config and/or log files etc. Steps to reproduce: run mkarchroot or makechrootpkg |
This task depends upon
Closed by Kristian (klausenbusk)
Saturday, 03 June 2023, 18:04 GMT
Reason for closing: Upstream
Additional comments about closing: Please report upstream if still relevant: https://gitlab.archlinux.org/archlinux/d evtools.
Saturday, 03 June 2023, 18:04 GMT
Reason for closing: Upstream
Additional comments about closing: Please report upstream if still relevant: https://gitlab.archlinux.org/archlinux/d evtools.
* Naming and format of lock files: We should be able to distinguish between different chroots. It should still be possible to run several instances of makechrootpkg simultaneously if they do not use the same chroot directory.
* NFS shares: As usual, the lock file mechanism will break if a chroot directory is shared (e.g. via NFS).