[Glass] Another metacello loading puzzle: xml

[monty via Glass]

I renamed enough packages to eliminate Monticello conflicts on GS:
	XML-Parser-GemstoneCompatibility -> XML-ParserGemstoneCompatibility
	XML-Parser-GTExtensions -> XML-ParserGTExtensions
	XML-Parser-HTML-Core -> XML-ParserHTML-Core
	XML-Parser-HTML-Tests -> XML-ParserHTML-Tests
	XML-Parser-HTML-GemstoneCompatibility -> XML-ParserHTML-GemstoneCompatibility
	XML-Parser-StAX-Core -> XML-ParserStAX-Core
	XML-Parser-StAX-Tests -> XML-ParserStAX-Tests
	Collections-OrderPreservingDictionary-GemstoneCompatibility -> Collections-OrderPreservingDictionaryGemstoneCompatibility

It's still an ugly mix of SS and Pharo "XXX-Core" + "XXX-Tests" names, but I wanted to change them as little as possible while maximizing preserved package history. I also did some Config cleaning, and #validate is a really great feature.

> Sent: Friday, January 26, 2018 at 10:45 PM
> From: "Dale Henrichs via Glass" <glass at lists.gemtalksystems.com>
> To: glass at lists.gemtalksystems.com
> Subject: Re: [Glass] Another metacello loading puzzle: xml
>
> Thanks Monty ... I use a slightly different pattern myself, but the 
> Seaside guidelines are definitely portable. Using these guidelines you 
> would rename XML-Parser-GemstoneCompatibility to XML-Gemstone-Parser and 
> that would eliminate the conflict with XML-Parser
> 
> Dale
> 
> 
> On 01/26/2018 07:37 PM, monty via Glass wrote:
> > Let me look into renaming at least the compatibility packages.
> >
> > I assume you're referring to these guidelines: https://github.com/SeasideSt/Seaside/wiki/Package-Naming
> > _______________________________________________
> > Glass mailing list
> > Glass at lists.gemtalksystems.com
> > http://lists.gemtalksystems.com/mailman/listinfo/glass
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>