Le 12 oct. 2015 à 21:17, Dale Henrichs a écrit : > > > On 10/12/2015 02:58 AM, Christophe Demarey wrote: >> >> Le 11 oct. 2015 à 22:32, Dale Henrichs a écrit : >> >> With our approach, metadata lies in the package for the current version and >> it is on the package repository when the version is released. >> Platform-specific packages could have their own dependencies. >> What will be possible is to create a new package (not a source code package >> but a package that is used by a package manager, i.e. metadata) to support a >> new platform and reusing existing code (by pointing to the package source >> code). >> Do you have an example to provide to me? >> >>> With all of that said, I really do love the idea of not having to support >>> Metacello anymore:) So I would like to see you succeed with your effort! >> >> It will take time ... >> I would really like to get feedbacks on Cargo because the knowledge you got >> with Metacello is invaluable. >> >>>>> Perhaps at this point in time, I'd like to read some code. Then I can >>>>> skip reading the paper and get a feel for how hard it will be to port to >>>>> GemStone:) >>>> I do not know where christophe save his code but it is be public. >>> I may not have time to read a paper ... but I would have time to read code:) >> >> http://smalltalkhub.com/#!/~demarey/CargoPackageManager >> <http://smalltalkhub.com/#%21/%7Edemarey/CargoPackageManager> >> > > While I think we might be trying to solve different problems ... I will take > a close look at the code in CargoPackageMananger ... too bad, the code isn't > on github, because it would be much easier for me to read, comment and > contribute:)
I have github in mind but did not yet take the plunge. I will see if can do it next days.
smime.p7s
Description: S/MIME cryptographic signature
