On 26 February 2013 20:07, stephane ducasse <stephane.ducasse@free.fr> wrote:
There is no magic if as a programmer we do not define the dependencies we cannot do anything. ;) so we should define configurationOf and we will take real advantages of them.
Now if you read the vision document you will see what we want:
we want a distribution that will be filled up automatically by executing configurations that are published in an inbox and validated (tests run, SmallLint rules run).
Then we will be able to have a one click install of projects that are certified to load in a given image.
Stef PS: SqueakMap failed because you had no idea is the package would load in your image. Believe me I know why I want the distribution infrastructure.
Oh, did you mean to type "you had no idea IF the package would load"? OK, sure, but that's not really SM's fault, that's just the way things were. Nowadays with CI and all sorts of stuff we're (Pharo _and_ Squeak, I mean) in a much better place. There's still the modularity aspect to worry about in the general case, but CI can still help out a bit there, flushing out incompatible monkey patches. frank
On Feb 26, 2013, at 7:33 PM, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
2013/2/26 Marcus Denker <marcus.denker@inria.fr>:
On Feb 26, 2013, at 5:33 PM, "Esteban A. Maringolo" <emaringolo@gmail.com> wrote:
If you count the number of packages in SmalltalkHub and compare them to the ones in Npmjs.org, it is impressive how much we have. But isn't "package" more like "repository" on smalltalkhub?
It is a Project, but on the explore screen it says Packages, so... who knows? :)
But it is true that GitHub is to SmalltakHub what npm/gem is to...?
Of course NPM's user base is two orders of magnitude greater, but we need to start having more killer app "modules", and some sort of guideline for those starting with Pharo and/or Smalltalk. And we need a system in the first place like that⦠smalltalkhub is more for code repositories, not in itself a repository of installable entities.
Yes, having packages as "artifacts" is more straightforward than the configurations and all that jazz.
The MetaRepo is going in that direction, but I still think that evaluating the install statements with Gofer or anything similar in a Workspace is somehow alien for a non smalltalker.
There should be something that wraps Gofer and works like the apt, npm or gem commands.
So there is a lot of work ahead⦠but we will get there.
No doubts of that.
Regards!