> As you can see I am still finding my feet here :) Amazing > though, that > during my research I didn't come across > http://squeaksource.com > squeaksource.com myself. I actually had come across > SqueakSource some time > ago when I started to look at Squeak. > > So, am I correct in assuming that SqueakSource was intended to replace > SqueakMap and Package Universe then? Since Pharo is a fork of Squeak, > wouldn't it need some sort of Pharo specific repositories or would all > SqueakSource repositories continue to work on Pharo? The > whole SqueakMap, > Package Universe, SqueakSource and Monticello is very confusing. > SqueakSource doesn't really look as inviting as Github either > ... I did see > there is a SqueakSource 2 project though.
It is all rather confusing but all these things seem to have different goals. From what I gather it's something like this... - SqueakMap: Meant as a distribution point for sharing published code in any format for any version of Squeak. The downside is it doesn't handle dependencies and is for sharing releasable versions, it's not a source code repository meant for development like squeaksource. The expectation is that if you see something in SqueakMap, it might work, it might not, it might with a bit of hacking and careful manual checking of possible dependencies. Was around before Monticello when people were still slinging sars and change sets for sharing code. SqueakMap is not meant to be a package manager, just a global single place to find all things squeak. - Package Universe: Seems to have been intended to be a version specific repository of packages and dependencies that are known to work in that particular version of Squeak. The expectation is that if you see something in Universe, it should work and will install any necessary dependencies. While this isn't always the case, most stuff seems to work pretty well. Admittedly, there's some overlap with SqueakMap here but it's really meant to be more like a package manager for your squeak image. It's comparable to apt-get or aptitude in Debian. - Monticello: Distributed version control and now the main format most squeakers share code in. Packages can be shared via package universe, squeakmap, and squeaksource. - SqueakSource: A public repository for the community to open and host Monticello projects. Of course, anyone can host their own such repositories as well and some do, but many big projects are on SqueakSource. Through here you be find the latest development versions, commit by commit, whether it's been released or not and can join and contribute code to these projects. You might have installed your software from squeakmap or package universe initially, but it's here you'll keep much of it up to date with the latest versions or find the latest bug fixes. Of course SqueakSource isn't as inviting as github, it has a vastly smaller community and mindshare than git and that's not going to change any time soon. Though we Smalltalk'ers keep hoping, Smalltalk still hasn't taken over the world and probably never will. As for Pharo and whether Squeak code from those places will work on Pharo, for now, yes, most of it does; however, as Pharo continues to grow and differentiate itself from Squeak, eventually it'll have to be considered a separate platform that is no longer Squeak compatible. That is rather the point, it just so happens the fork is recent enough that it's still basically Squeak 3.9 but that won't last forever. Pharo is not Squeak, so it'll be interesting to see how much of the community it captures and it all unfolds. Me, I'm just a working programmer and this is all just my opinion, but that's how it all looks to me. Squeak paid my bills, Pharo is replacing it. Good riddance to the silly mouse, name, and look, and hello to a serious business oriented open source Smalltalk that I'm not embarrassed to mention to clients. Ramon Leon http://onsmalltalk.com _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
