You are not logged in.
Pages: 1
If Pacman when it gets to a file conflict(e.g. when a file already exists), it just stops and tells you what files are conflicting. It would be a cool feature if it would ask you if you want to overwrite the file, or not. For example it might say:
File already exists: "/usr/bin/bash" Overwrite? [Y/n]
Just an idea
Mark
"power corrupts, and absolute power corrupts absolutely" -Lord Acton
Offline
Too much verbosity. From what I gather (and I'm only a relatively new linux user, about 1 year), the Unix philosiphy is less output is more. I've seen people here saying they reckon the progress bars on pacman -Syu is too verbose... I can't see this getting past them
Offline
markw - yeah - great for one file - what if it is 200 files that you have sit going
n
n
n
n
n
n
n
y
n
n
n
n
...
Offline
everyone's gotta have an "improvement" for pacman regarding config files.
i recently gathered the opinion that this is entirely not pacman's fault, but the contents of the package. a program should never include a default configuration file, but provide an EXAMPLE. that way, you will never overwrite your config.
optimally, this should be fixed upstream by the software developpers, but that's not likely to happen. if packagers agree with me, it would be possible to rename packaged config files to config.file.example.
but i'm not counting on that either.
Offline
I guess I'll just use the "-f" option when I need it then.
Thanks for your input guys
Mark
"power corrupts, and absolute power corrupts absolutely" -Lord Acton
Offline
Pages: 1