I'm running into a bit of complication with code that is already loaded in GToolkit (but not Pharo) (e.g. XPath, XML-Parser, OSSubprocess) creating conflicts for users.
One option is to include an `#onConflict:` in the readme. However, this seems less than ideal because it doesn't cover being loaded as a dependency.
What I'm doing now is e.g.
```
spec
for: #( #GToolkit )
do: [
spec removeProject: 'OSSubprocess'.
spec
package: 'Tesseract' overrides: [
spec requires: (tesseractBaseDeps copyWithout: 'OSSubprocess') ] ]
```
However, it feels a bit like jumping through hoops. I'd rather add the requirement just on Pharo than remove it on GToolkit. The issue is that GT is a custom platform attribute.
So it occurred to me that one of two things would be helpful:
1. Make GToolkit a full-fledged platform (but not sure if there is a built in extension point for this
2. Say (pseudocode): `spec for: {{not GT}} do: ...`
Thoughts?