| Ensuring update path after feature refactoring [message #775314] |
Thu, 05 January 2012 18:56 |
 Jeff Johnston
Messages: 215
Registered: July 2009 |
Senior Member |
|
|
I working on transferring the Autotools feature plus its set of plug-ins from the Linux Tools project into the CDT project for Juno. I would like to ensure a smooth update path for existing Autotools users.
The idea I came up with is to create a shell feature for the next update of the Linux Tools feature (possibly also the plug-ins) such that the shell feature/plugin requires the new CDT versions. When a user updates, they will require the new CDT feature and from then on they will see updates to it as I intend to let the shell feature be the last release under Linux Tools.
I would like to also prevent the old Autotools from being installed at the same time as the new Autotools but I'm not sure how to specify conflicts or obsoletions.
Any p2 suggestions for this or issues I haven't thought of?
|
|
|
Powered by
FUDForum. Page generated in 0.03217 seconds
] 
Search
Help
Register
Login
Home
