On Apr 02, Joey Hess <[EMAIL PROTECTED]> wrote: > On reviewing how these links are supposed to work, I don't understand > why these symlinks are used at all. If files were placed directly in Because they allow changing the order in which files are processed, which may be useful. Or at least appeared to be useful when I designed this.
> /etc/udev/rules.d and were conffiles, then admins could simply directly > remove them and they would not be put back on upgrade due to normal > conffile handling. (hal already handles its rules file this way FWIW.) hal is buggy... > Is there actually a good reason for the symlinks, which I am not > seeing? The best reason I have come up with so far is that it allows the > link to be renamed to a higher/lower number while still having the file > contents updated by dpkg. Indeed. > With the symlinks, the best approach I've come up with for postinst > scripts is for them to check for a flag file, create the symlink and > touch the flag if the flag is missing. I'm not sure where to put the > flag files, possibly somewhere under /var. How this would be best? The current practice of creating the symlinks only when the package is installed for the first time (or upgraded to a version which includes the symlink if it did not exist before) is much simpler. -- ciao, Marco
signature.asc
Description: Digital signature
