Hernán, thanks for the contribution, I copied it to the repository. I think you can commit without any special permission. I took a look in the errors and I found that it uses SourceFilesArray API that we removed in Pharo 5.0... indeed, in Tanker we made strong assumptions about the changes files. I did a pass migrating code to current Pharo (50249). Mariano: yes, we didn't implement recompilation when something changed in the format. Max: I agree Tanker has to use RPackage instead of PackageInfo, but I'm not sure it needs to be moved to Ring. MartÃn El jue., 20 ago. 2015 a las 21:22, Max Leske (<maxleske@gmail.com>) escribió:
On 20 Aug 2015, at 20:49, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Hello Max,
2015-08-20 15:15 GMT-03:00 Max Leske <maxleske@gmail.com>:
On 20 Aug 2015, at 19:38, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Hello MartÃn
2015-08-20 5:31 GMT-03:00 Martin Dias <tinchodias@gmail.com>:
Hello Hernán,
It's outdated, we were not taking care of Tanker. I've just updated some urls in the doc, and the Pharo versions in the Jenkins job (it was being run in 2.0 and 3.0!).
BTW, have you loaded it from this repo?
Yes.
I checked the code and PackageInfo usage was intentional (#behaviorsLocalToPackageInfoNamed: , #extensionMethodsToPackageInfoNamed: , etc) , but the tests are generating AnObsoleteClassForTestToBeDeleted... and from there I don't know.
Thatâs something weâve fixed in Fuel. Itâs simply a side effect of the tests, not a functional problem.
Good :)
Is just that PackageInfo stuff preventing to use Tanker?
I guess Tanker would need to be updated for the changes in CompiledMethod and possibly a couple of changes would be required to account for deprecation etc. Iâm not sure how much work it would take to use RPackage / Ring.
I hope it is not too much work.
Could you comment how far is Tanker from being stable or usable?
I guess we could make it work within a couple of hours / days. So far there was simply no interest from anybody AFAIK.
Whatâs your use case exactly?
Building my PhyloclassTalk app loads > 60 packages and it is taking too much time. I read about loading Seaside in 10 sec. so I want that too :)
Well yes but thatâs only possible if you first export the code in the Tanker format. And you donât want to do that for every new version (unless of course, Tanker were the default formatâ¦).
Another situation is when I show Pharo to solve "easy" tasks (CSV, PetitParser, etc) to people and it doesn't feel nice to wait loading, specially when Python takes 2 secs to install with pip, or they use IPython/anaconda which has everything preloaded.
I know what you mean. We have builds on our build server that take up to 30 minutes. I once thought to have multiple stages of builds to reduce build times but that wont work in this case of course.
Cheers,
Hernán
Cheers, Max
Hernán
(we moved from Mariano's repo, but the old one wasn't deleted).
Cheers, MartÃn
El jue., 20 ago. 2015 a las 8:24, Hernán Morales Durand (< hernan.morales@gmail.com>) escribió: Hello,
What is the status of Tanker? I tried to loadDevelopment in Pharo 4 but there are references to PackageInfo, and tests fails. Cheers,
Hernán
<TankerPackagesSupport-HernanMoralesDurand.11.mcz>