FS#8054 - "Dynamic" IgnorePkg
Attached to Project:
Pacman
Opened by Corrado Primier (bardo) - Tuesday, 18 September 2007, 15:36 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 14 November 2007, 23:14 GMT
Opened by Corrado Primier (bardo) - Tuesday, 18 September 2007, 15:36 GMT
Last edited by Aaron Griffin (phrakture) - Wednesday, 14 November 2007, 23:14 GMT
|
Details
It would be nice if the --ignore list could be updated at
runtime, while a specific package is downloading.
For example, I have some core updates to do and I want them done quickly, while at the same time I have to upgrade openoffice, firefox, java, kde and other big packages. Writing a pacman line to ignore these packages can get more time than it is needed to download and install everything, and forces the user to -Syu, Ctrl+C and "-Su --ignore x --ignore y...". This feature would allow people to press a shortcut that tells pacman to stop downloading $hugepackage, and adding it to the ignore list, so that it can be upgraded at a later time. Of course, some care must be taken: if the skipped package is a dependency for another package on the upgrade list, and there's a version dependency, the other package should be skipped as well, and the user must be notified. In my ALPM ignorance I suppose it is equivalent to a dependency recalculation. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Wednesday, 14 November 2007, 23:14 GMT
Reason for closing: Implemented
Wednesday, 14 November 2007, 23:14 GMT
Reason for closing: Implemented
I, for one, don't like any more interactive complexity into the equation.... perhaps there is another way we can solve your problem?
[...]
Targets: foo bar foobar barfoo
Proceed with installation? [Y/n/s] s
Do you want to install foo? [Y/n] y
Do you want to install bar? [Y/n] y
Do you want to install foobar [Y/n] n
Warning: bar depends on this version foobar, it won't be upgraded now
Do you want to install barfoo? [Y/n] y
Targets: foo barfoo
Proceed with installation? [Y/n/s] y
[...]
As you can see it is a little clumsy, and I don't really like it.
This can be easily done in a GUI frontend by selecting/unselecting packages to upgrade. Then that GUI frontend can easily recalculate required dependencies and select missed dependencies automatically.
I like the comma idea though, that sounds easy and doable - I will mark this down as "due in 3.1"