[question] How is zinc versioned?

[tukanos]

Hello @svenvc ,

I wonder how do I know which version of zinc do I have? Is there a simple way to find out a version?

Thank you.

[svenvc]

I do not know if there is an easy way to find out what the latest version is of any Pharo package.

I always load the latest version from https://github.com/svenvc/zinc

The Zinc version inside Pharo is not up to date, and partially modified, though more in style than in substance.

[tukanos]

I do not know if there is an easy way to find out what the latest version is of any Pharo package.

I always load the latest version from https://github.com/svenvc/zinc

The Zinc version inside Pharo is not up to date, and partially modified, though more in style than in substance.

Depends if there is any package manager used. I have found there is Pakbot which could help with that. Thou, I don't know if it is maintained.

I see you use always the latest version from master? I see there are some tags used like v3.0.1, v4, v5. I should disregard those?

I see, Zinc inside Pharo is not up-to-date, good to know.

[noha]

I do not know if there is an easy way to find out what the latest version is of any Pharo package.

I always load the latest version from https://github.com/svenvc/zinc

The Zinc version inside Pharo is not up to date, and partially modified, though more in style than in substance.

Depends if there is any package manager used. I have found there is Pakbot which could help with that. Thou, I don't know if it is maintained.

I see you use always the latest version from master? I see there are some tags used like v3.0.1, v4, v5. I should disregard those?

I see, Zinc inside Pharo is not up-to-date, good to know.

There is a package manager (metacello) involved usually. In case of git you can see the version being loaded either as tag or commit hash. Or directly in the BaselineOfXXX package that depends on the package that has been loaded. Pakbot got stalled in development (which is a pity) because there are not enough engineers available and other things got a higher prio. To me this is one of the next important things to be able to work with the current ecosystem.
Also a pity is that pharo devs copied Zinc into the pharo core. This is really a bad idea especially they apply pharo refactorings on it. But it is also a necessity because pharo loads stuff via http on bootstrap.
So there is a bunch of possible solutions. I wanted to talk to @svenvc already if zinc cannot be split into a basic GET requester habdling just the socket and the rest of zinc. Pharo could copy the basic stuff and leaves the rest of the package intact which should make it way easier to maintain.
And pakbot should solve the metacello shortcomings being a recursive package manager which cannot work pretty welll

[tukanos]

There is a package manager (metacello) involved usually. In case of git you can see the version being loaded either as tag or commit hash. Or directly in the BaselineOfXXX package that depends on the package that has been loaded. Pakbot got stalled in development (which is a pity) because there are not enough engineers available and other things got a higher prio. To me this is one of the next important things to be able to work with the current ecosystem. Also a pity is that pharo devs copied Zinc into the pharo core. This is really a bad idea especially they apply pharo refactorings on it. But it is also a necessity because pharo loads stuff via http on bootstrap. So there is a bunch of possible solutions. I wanted to talk to @svenvc already if zinc cannot be split into a basic GET requester habdling just the socket and the rest of zinc. Pharo could copy the basic stuff and leaves the rest of the package intact which should make it way easier to maintain. And pakbot should solve the metacello shortcomings being a recursive package manager which cannot work pretty well.

@noha Thank you for your answer.

Yes, I'm aware that you can use Metacello to load tag or commit. That usually is good only for development or at least I think so. It is much better to have Pakbot's semantic versioning is much better on updating production systems because you know what package version you should be at.

I noticed that Pakbot got sidelined because I have sent a PR, but nothing happened even after quite some time. I think it would be really beneficial to have Pakbot in the Pharo's ecosystem.

While I understand they have to have some minimum functionality there, I'm not sure that it is a bare minimum, anyways you can always overwrite it with your own load.