You are not logged in.
Pages: 1
I'm sure this gets asked all the time, but I can't find any reference to it in the wiki, forums, website, google, etc.
Is there way to get pacman to tell you what it would try to install without really trying... like gentoo's: emerge --pretend.
Thanks a lot.
Offline
Most of the time people always reply to just do <code>pacman -Syu</code> and then answer no once the package list comes up, but agree with you that there should be an option to do a dry run...that way you won't accidentally install stuff if you should happen to hit <code><ENTER></code> by mistake. I just never had the guts to bring it up myself
Offline
Stick a feature request on the bugtracker - it might get into a future release.
Offline
I never thought it was needed, if you try to install something it'll always list the packages to be installled and ask your for Y/N, is that not what emerge -va does?
Offline
whats wrong with answering "no" after a pacman -S <pkg> ??
If its more work then consider the extra dash and letters to type out --pretend
Offline
It would probably be implemented as -p as well as --pretend.
(FWIW, I don't think it's really necessary. On the other hand, I doubt it would be hard to implement... Still, better to let the maintainers alone in this case I think.)
Offline
I think it's better than just saying no for a couple of reasons...one it could potentially be run without root access (like <code>pacman -Ss</code> is now), and also it would prevent you from accidentally upgrading when you weren't ready to do so. Right now, if you happen to hit <code><ENTER></code> at the prompt, it will choose yes by default and install the packages. Having the ability to see what needs upgrading before hand could prevent mistakes. It could even be in a format that gives you a little more information like what your current version is and what it will go to:
ruby 1.8.3-1 --> ruby 1.8.4-1
If you're familiar with DarwinPorts (a package management system for OS X), they use a syntax that's fairly parallel to pacman, but add the option to do something similar to this with: <code>port outdated</code>. Anyway, I could see a lot of use for it...
Offline
I agree this would be useful.
I tend to check carefully what -Syu wants to upgrade, and if there are things in the list like a new kernel/xorg/kde i usually do the other updates first before applying those.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
it would prevent you from accidentally upgrading when you weren't ready to do so
Control-C. I think it's unnecesarry too. About priveleges, you have to be root to upgrade anyway - so if you're not sure if you want to upgrade, you can watch the list through "su -c" or sudo and avoid the extra step of re-running pacman in case you want to install the updates. If not, press N as said.
Offline
It's not the same as canceling out of a "-S"... First of all, you wouldn't need to be root to do it. Second, sometimes pacman -S doesn't tell you what you need to know until after you say "Y" ...
For example on "pacman -S kde" it will tell you that it's going to install "arts" and "kde-common," I'd like to know what version it wants to install, etc.
Right now, I do "sudo pacman -S kde," then say "Y," then cancel when it tells me what is going on... not the ideal solution.
I agree that it's not real important, but I was just asking if there was a way to do it.
Offline
Added a feature request to flyspray...
Offline
Another couple of points...if there were one package listed per line, it would be easy to grep, which in turn could make it easier to do scripting with the information (you could make custom adesklets, send yourself emails on important upgrades, etc.). It would also give a quick way to check on people's setup when they ask questions in the forum (i.e. we could just ask them to run <code>pacman -Su --pretend | grep perl</code>), or it could even have the ability to check on individual packages: <code>pacman -S --pretend perl</code>.
I equate it with something like <code>tar --diff</code>...by some people's arguments, why would anyone need it if they could just do <code>tar --list</code> and see what's in there, or watch during the unpacking and hit <code>Ctrl-C</code> if they saw something they didn't like? Why would any command line programs have a dryrun option?
Anyway, that's my $0.02, and I guess it's in the dev's court now...
Offline
Thanks for making that feature request elasticdog. Also, I totally agree with making it more scriptable. That would be incredibly useful.
Offline
I think this would be useful as well. I don't update like I used to on gentoo, so it would be neat to send myself an email every morning listing possible package upgrades. I know you can do this with a little yes -n | pacman -Syu fun, but really, I think that it's a useful feature to be built in.
Offline
Pages: 1