Conflicting implementations exist for #extractAllIn: for ZipArchive

[Rinzwind]

There are conflicting implementations for #extractAllIn: for ZipArchive in the ‘pharo’ and ‘NewTools’ repositories. This leads to confusion when committing as only of the two implementations can be loaded in the image and the one in the other repository is unexpectedly shown in the commit window as being removed.

[Rinzwind]

Other conflicting implementations: #settingsOn: for NECPreferences in ‘pharo’ and ‘NewTools’, #possibleSolutionsForInput: on MethodFinder in ‘pharo’ and ‘NewTools’.

[hernanmd]

I don't know why extractAllIn: is still in Pharo repo, it should be in NewTools-Compression-Utils (pharo-spec/NewTools@ef9aad0)
I will make a PR to remove it from Pharo.

[astares]

@hernanmd Shouldnt it be the other way around: have it by default already in standard Pharo and remove the extension in NewTools.

Because it is usuable in a wider scope to deal with ZIPs (also in smaller images that just have ZIP but not NewTools)

[hernanmd]

@hernanmd Shouldnt it be the other way around: have it by default already in standard Pharo and remove the extension in NewTools.

Because it is usuable in a wider scope to deal with ZIPs (also in smaller images that just have ZIP but not NewTools)

This was already discussed in the context of removing UIManager references, because this method was using UI.

[astares]

Answering to myself: ok - it opens a dialog (StOpenDirectoryPresenter) to ask for the target folder. So yes - it should be part of NewTools only