Am 25.11.2011 16:47, schrieb Dave Reisner:
> Well, ideally, on -S --dbonly if there's a file conflict, the packages
> will also have a conflicts= (which will still be honored). Yes, this is
> all extremely hackish and shouldn't be used. Never the less, if you're
> performing an operation on the DB only, it really should be on the DB
> only.

Ideally, pacman would ignore file conflicts in the file system only if
the files do not belong to any package. If the conflicting files belong
to an installed package, it should still abort and require -f.

Attachment: signature.asc
Description: OpenPGP digital signature



Reply via email to