There are many packages in Pharo (e.g. Spec) that don't have any explicit version outside of the commit number - because it's integrated nobody is bothered with release management (this is not a good thing but it is less work). My guess is that SUnit is in the same state. On Wed, Apr 15, 2015 at 9:09 PM, Dmitri Zagidulin <dmitri@zagidulin.net> wrote:
That was my first thought, too. But I couldn't find ConfigurationOfSUnit (by any spelling) anywhere. (Not in the base image, not in the configuration browser). And I couldn't find it in the main Pharo repo.
There's this: http://smalltalkhub.com/#!/~SUnit/SUnit but the description for it says 'This project is hosting the old squeaksource SUnit project.' so I wasn't sure if that's the repo that is used for Pharo core.
On Wed, Apr 15, 2015 at 2:46 PM, kilon alios <kilon.alios@gmail.com> wrote:
You could take a look at the available configuration, there are usually version methods in the instance side like for example
version10: spec <version: '1.0' imports: #('1.0-baseline' )>
On Wed, Apr 15, 2015 at 7:24 PM, Dmitri Zagidulin <dmitri@zagidulin.net> wrote:
How does one go about finding the version numbers of core libraries like SUnit that are included in a particular Pharo distribution?
(What prompted me to try and find out is that at the start of the SUnit chapter in UPBE, it says "In the future, Pharo may include version of SUnit4.0." And I was curious whether Pharo 4.0 includes that newer version of SUnit, etc. But I'm also curious whether there's a general procedure or convention for finding versions of external libraries that are also pulled into Pharo core.)