GNU bug report logs -
#49261
28.0.50; File Locking Breaks Presumptuous Toolchains
Previous Next
Reported by: Mallchad Skeghyeph <ncaprisunfan <at> gmail.com>
Date: Mon, 28 Jun 2021 18:28:02 UTC
Severity: normal
Found in version 28.0.50
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #32 received at 49261 <at> debbugs.gnu.org (full text, mbox):
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Thu, 01 Jul 2021 12:55:55 +0200
> Cc: 49261 <at> debbugs.gnu.org
>
> Mallchad Skeghyeph <ncaprisunfan <at> gmail.com> writes:
>
> > ...even if the lock files are symlinks (which they not necessarily
> > are), we need to handle the case of several files with identical
> > basenames in different directories. (Their being symlinks is
> > unimportant, because the target of the symlink doesn't exist.)
> >
> > Actually, is there even a good reason to keep relying on symlinks in the future?
> > Considering that.. ahem, some Operating Systems cannot do symlinks for the
> > user?
> > If it were treated as a normal file you could load it up with whatever metadata
> > you want.
>
> Using a normal file should also work, I think? But it'd be slightly
> less efficient on some common popular file systems.
We already use regular files on systems on which symlinks are either
unsupported or otherwise problematic.
This bug report was last modified 3 years and 305 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.