I was in rush when I wrote the first answer
I thought xml support is already migrated by Sven?
https://github.com/svenvc/XML-Support-Pharo <https://github.com/svenvc/XML-Support-Pharo>
Or do I mix something up here?
Sven did not migrate the history
------------- Something else: In case someone wants to use it: I used Peters nice migration tool for ... http://smalltalkhub.com/#!/~PharoExtras/LDAP/ <http://smalltalkhub.com/#!/~PharoExtras/LDAP/> ... and put it to: https://github.com/a2b-alb/PharoExtras-LDAP <https://github.com/a2b-alb/PharoExtras-LDAP> I don't know if this is the right place or if you would rather have it under ... https://github.com/pharo-contributions/ <https://github.com/pharo-contributions/> ... or somewhere else.
Thanks and it would be good.
I do not know what is the best process to add something to pharo-contributions. May be we should fork your version and put it there and that people continue to contribute using PRs. What do you think?
------------- I started trying to do the same migration process for ... http://www.smalltalkhub.com/#!/~Pier/Pier3 <http://www.smalltalkhub.com/#!/~Pier/Pier3> ... but I failed on errors loading older mcz files:
"instance of ByteString did not understand #peek" on: MCMczReader >> contentsForMember: (ZnInvalidUTF8: Illegal leading byte for utf-8 encoding)
Is this wrong encoding or corrupted files
How to treat these files ? -> Is just ignoring this majority of failing mcz files via migration ignoredFileNames: #() ok ?
I wonder if the MCMCZ was not about the delta between two commits but may be Iâm wrong. BTW this is great to see someone pushing pier. I would like to see how a new version of pillar can be pushed back into pier.
------------- As a workaround I then left the history versions behind and took only the newest mcz files. But I am not sure which package version "is in harnmony" with the other ones... ;-) -> While trying out which versions of the ConfigurationOfPier3 load in a p7 image only the #stable one loaded without problems. The newer ones didnât.
Seriously for Pier I would first focus on making it work with the latest version and we can always say that the historuy is in another repo.
I did this by first loading as much pier3 dependencies (seaside, magritte, ...) from the new github repos. So I can then say ... onConflict: [ :e | e useLoaded ]; ... when loading pier3 from smaltalkhub.
Can someone who knows pier3 better than me, give me a hint on which package versions combinations are the ones to go with ? -> Is to just start with the newest mcz files the way to go? Or should I use the #stable ConfigurationOfPier3 ?
Use the configuration because I have no clue. Esteban was extending pier in the past.