upgrade with archivemode

We had some discussion about changing the upgrade action for archive  
mode to 'unarchive' from 'archive'

I remebered that it broke my not-quite-ready remote archive patch,  
but I didn't remember that it also altered the sequence of events (at  
least on my non-image mode install, I haven't tested this yet on my  
image-mode install).

When upgrade_action is set to 'archive' we get this sequence of events:

fetch/configure/build/destroot/archive new version
uninstall old version
install new version

With upgrade action set to 'unarchive' (as it is currently) we get  
this sequence:

uninstall old versino
fetch/configure/build/destroot/archive/install new version

This was the reason why I had originally set it to 'archive' (as it  
then more closely mimics the behavior of the image mode version and  
minimizes the time when no port of any version is installed).

Changing it to 'unarchive' allows one to copy archives over and have  
upgrade 'just work', so changing it back will also lead to some  
undesired behavior (but less undesired I think, and probably easier  
to fix the archive target to check for an existing archive and not re- 
create it without force than to modify the sequence of events for the  
unarchive target).

Thoughts?
--
Daniel J. Luke
+========================================================+
| *---------------- [email protected] ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
|   Opinions expressed are mine and do not necessarily   |
|          reflect the opinions of my employer.          |
+========================================================+

_______________________________________________
Darwinports mailing list
[email protected]
http://www.opendarwin.org/mailman/listinfo/darwinports