Comment 8 for bug 522910
Revision history for this message
| Nathan Stratton Treadway (nathanst) wrote Re: hardy installation fails to take direct route to lucid | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Great, thanks.
The reason I suggested moving the explaination to the README was to avoid dpkg "Configuration file modified since installation" messages during future package upgrades.
Obviously one round of such manual intervention is unavoidable (for anyone who has changed already the file from its original installed form), but if the full description of the various supported options is moved into the README file, it could be changed/expanded later without triggering the changed-conffile situation again....
Related to that, I noticed that Bug #543165 has been marked as a duplicate of this one. However, I see that that request actually goes a few steps further: the idea there is that the upgrade manager would recognize that the currently-running release is an LTS and automatically check for both the next release and the next LTS release, and if both were available the user would then be presented with the choice as to which target release to upgrade to.
Obviously that would involve new logic in the upgrade-manager code... but if such a thing were eventually implemented, presumably the description text that you have just updated would need to be changed again....