I wasn't aware of LDAP support in Pharo. Thanks for porting it. Wouldn't it be better to call the repo "pharo-ldap"? When my repositories are Pharo specific and don't have a fancy project name I name them "pharo-something", e.g. "pharo-couchdb", "pharo-base58", "pharo-bip39mnemonic", etc. Regards, Esteban A. Maringolo El vie., 8 mar. 2019 a las 8:45, Albrecht Baur via Pharo-users (< pharo-users@lists.pharo.org>) escribió:
Hi, In case someone can use it: I used Peters git migration tool for ... http://smalltalkhub.com/#!/~PharoExtras/LDAP/ ... and put it to: 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/ ... or somewhere else.
------------- here the question: I started trying to do the same migration process for ... 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 ?
------------- 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 harmony" 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.
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 ?
best, Albrecht