Community
Participate
Working Groups
I must admit that I like the new target provisioner. Now that it is so slick and easy to download things that the only thing that I wish was there is a "check for update" button. This way it becomes super trivial to keep the target up-to-date as well. Remember there is almost everything in p2 to do this (hint, hint)
Would be slick, though might be hard to fit it nicely into the UI as many targets do not use p2 and cannot be updated. Will consider for 3.5, but no promises.
Couldn't we do this via the set target operation? If there's nothing in the bundle pool, we know it's not an update.
(In reply to comment #2) > Couldn't we do this via the set target operation? If there's nothing in the > bundle pool, we know it's not an update. This is a feature request to "check for updates" to a target definition. I.e. if it comes from a repo, see if there is a newer version. Just like you would do to your running host. The question is how to fit this into the UI nicely.
Nice, but this is a new feature so we must defer to 3.6
I'm also eagerly waiting for this feature (although I don't care in which release it will be). Will automatic update also be included in this feature or should I open a separate bug?
This would be easier if targets were profile based (Bug 287619).
Created attachment 181680 [details] initial patch to update targets This is a first cut at updating a target. there is an Update button in the TargetLocationsGroup that calls an UpdateTargetJob. This simply scans through all IUBundleContainers looking for any feature and then looks for the most recent version of that feature. That new version is then used. If the feature being updated is the current one then we automatically call LoadTargetDefinition. Issues: - UI integration is rough. The dirty flags and workflow need better integration - Not clear that we want to automatically update the current target. Could be expensive (causes a build) and there may be other edits or review to be done by the user. flipside is that one button update makes it real "slick". - might consider showing the user what is going to change (deluxe) - Note that updating may cause a version drop if the latest things are not available - likely some robustness topics if things are missing etc - Affordances for 0.0.0 in the .target file are there but complicate things a tad. If we are not going to really support that then the code can be simplified a bit.
A slightly updated version of this patch has been consolidated with several other overlapping patches and attached to bug 328929. discussion of issues related to this enhancement should continue here. The consolidated patch is just to ease application.
*** Bug 235420 has been marked as a duplicate of this bug. ***
Fixed in HEAD. Thanks for all the great work Jeff!
Verified in I20101208-0800 Still would be great to have people try out their own use cases to make sure this works well for them.
