Hi
I value the idea that when we look for a software (for example SIXX)
we can find a version that is working. In the past we used Universes and
if was successful.
We cannot not have squeakmap and universe at the same time.
I discussed with damien briefly about that and he told me that we coud
Hi Stef,
I know I am not Dale, but I will give my two cents anyway :).
I believe Metacello is a very nice piece of work and it should be a
very strong contender for managing releases. The ui tools are not
quite there yet, but it works very nicely for allowing someone to
specify the exact
On Wed, Sep 16, 2009 at 11:38 AM, Tudor Girba gi...@iam.unibe.ch wrote:
I believe Metacello is a very nice piece of work and it should be a
very strong contender for managing releases. The ui tools are not
quite there yet, but it works very nicely for allowing someone to
specify the exact
Ok but for pharo1.0 it would be nice to have it :)
then after we plug metacello underneath
Doru with metacello will we be able to say
I want to load in the past the version of moose which worked with
pharo1.0
even if now I'm working on pharo 3.2 (the real future :))
Stef
On Sep
Basically yes, but for that we just need a way to manage Pharo
versions. So, as long as we can say what Pharo 1.0 is, we should be
able to do that.
Cheers,
Doru
On 16 Sep 2009, at 13:29, Stéphane Ducasse wrote:
Ok but for pharo1.0 it would be nice to have it :)
then after we plug
I am interested in learning how we could use metacello. Not for 1.0.
Before we commit to it for 1.1 I think we would need to conduct an
experiment in parallel to get a feel for it. We should also review the
other proposals. Then commit to one proposal for 1.1 1.2 etc and make
the process
I agree. Universes is cool but:
- it requires a dedicated server and only few people installed one already
- it only allows one administrator per package description
Setting up an Universe server is simple: Just put the XML package
definition on some public HTTP server and version it with
My 2 cents.
It's very cool what there will be a packaging system. But i think what
it should allow distribution not only code, but asets too. Like
images, or css (for web application)
On Wed, Sep 16, 2009 at 15:59, Michael Robers m...@mjr104.co.uk wrote:
am interested in learning how we could
Mike
Yes this is a good idea.
read the blog of dale.
We are starting to manage all our project Moose, Mondrian, Glamour
with metacello
I'm waiting that doru and dale release a version with fixed api to
write a chapter for
Pharo by example2
Stef
On Sep 16, 2009, at 1:59 PM, Michael Robers
Stef,
I think that the core of Metacello is very solid. Doru is using it for Moose (a
large project) and I am using it for GLASS managing 20 some individual projects
like Pier, Seaside 2.8 and Magritte. I am working on a Metacello configuration
for Seaside 3.0 - almost 70 packages and around
Stef,
Under Metacello, when you a release a version, the complete list of Monticello
files are recorded with the version (including load order dependencies).
So Metacello is designed to make it possible to load old versions of projects
into new images.
It is also possible to record the
I remembered that. Now I was wondering about the following
if we can tag a config we get in essence an Universe: a set of
packages wrking with a given tag.
But this is not quite the same.
One of the problem that universes solved is that if
MyApp requires
AppA v1
YourApp requires
When defining project references in Metacello, you can use a #= operator which
basically says that later versions are okay - this makes it possible for MyApp
to specify AppA v1 but be able to use AppA v3 if it is already loaded...
The problem of conflicting requirements isn't solved but
13 matches
Mail list logo
