Port upgrade problems when port installed but not active

[jberry@…]

Closing bug... I accept Ole's explanation.

[jberry@…]

If you issue a port upgrade on a port that is active but not installed, it first activates the port, then immediately turns around and deactivates it.

This is somewhat wierd, takes extra time, but is perhaps not actually harmfull.

Here's a log of doing just that for ImageMagick. Note that ImageMagic is installed but not active at the start. Note also that the ImageMagick installed ultimately fails, though that's due to problems with the ImageMagick port.

Log is attached.

[jberry@…]

Log

[jberry@…]

Note that I understand it probably wasn't intended that you'd be able to upgrade a port that was not active. So this could just be a case of "well, that's a stupid thing to try in the first place!". I did it by accident, honest! But it would be nice if port upgrade would sense this situation and handle it gracefully.

[olegb@…]

(In reply to comment #2)

Note that I understand it probably wasn't intended that you'd be able to

upgrade a port that was not

active. So this could just be a case of "well, that's a stupid thing to try in

the first place!". I did it by

accident, honest! But it would be nice if port upgrade would sense this

situation and handle it gracefully.

it is intended - what upgrade does is make sure all versions of the port is deactivated an then activates the newest version.

then it checks if there is a newer version in the tree - if so, it deactivates the active one and builds (and activated the new one). if there is no new version in the tree all is ok, and upgrade exists.

(all this is from memory, so it could be flawed), but - upgrade was designed like that - and, yes in the case where you upgrade a port that isnt active, it seems stupid, but it was correct. and it is the (fastest?) way tho deal with the other cases where there are multible installations of the same port and you dont know which one is the newest or if the newest is activated.