Suppressing the No Changes confirmer during update

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Suppressing the No Changes confirmer during update

Eliot Miranda-2
Hi All,

   I guess because of the multiple ancestors in the Spur bootstrap packages whenever I update a Spur image I see lots of annoying "No Changes" confirmers popping up that have to be clicked on to continue.  They come from

resolveConflicts
(records allSatisfy: [:ea | ea isAncestorMerge]) ifTrue: [MCNoChangesException signal. ^ false].
^ ((MCMergeResolutionRequest new merger: merger)
signal: 'Merging ', records first version info name) = true

I see a handler for MCMergeResolutionRequest in 

upgrade
^self depsSatisfying: [:dep | dep isFulfilledByAncestors not]
versionDo: [:ver | 
(self class upgradeIsMerge and: [ver shouldMerge])
ifFalse: [ver load]
ifTrue: [[ver merge]
on: MCMergeResolutionRequest do: [:request |
request merger conflicts isEmpty
ifTrue: [request resume: true]
ifFalse: [request pass]]]]
displayingProgress: 'upgrading packages'

am I right to think that's also the place to put a handler for the MCNoChangesException notification?
--
best,
Eliot


Reply | Threaded
Open this post in threaded view
|

Re: Suppressing the No Changes confirmer during update

Bert Freudenberg

On 15.05.2015, at 00:52, Eliot Miranda <[hidden email]> wrote:

Hi All,

   I guess because of the multiple ancestors in the Spur bootstrap packages whenever I update a Spur image I see lots of annoying "No Changes" confirmers popping up that have to be clicked on to continue.  They come from

resolveConflicts
(records allSatisfy: [:ea | ea isAncestorMerge]) ifTrue: [MCNoChangesException signal. ^ false].
^ ((MCMergeResolutionRequest new merger: merger)
signal: 'Merging ', records first version info name) = true

I see a handler for MCMergeResolutionRequest in 

upgrade
^self depsSatisfying: [:dep | dep isFulfilledByAncestors not]
versionDo: [:ver | 
(self class upgradeIsMerge and: [ver shouldMerge])
ifFalse: [ver load]
ifTrue: [[ver merge]
on: MCMergeResolutionRequest do: [:request |
request merger conflicts isEmpty
ifTrue: [request resume: true]
ifFalse: [request pass]]]]
displayingProgress: 'upgrading packages'

am I right to think that's also the place to put a handler for the MCNoChangesException notification?

Sounds right.

- Bert -






smime.p7s (5K) Download Attachment