2010/12/9 Chris Muller <asqueaker at gmail.com>:
>> My rationale: Why shouldn't we use Metacello Configs if
>> they are there and doing what we want: Installing the
>> software.
>
> -1.  My preference is to stay simple.  Just use Installer scripts to
> load a configuration of exact-versions that work together.
>
> A separate Installer script could be used to "merge the latest
> versions" if people want that.
>
> I don't see the need to introduce Metacello for these simple requirements.
>
>  - Chris
>

As I understand it, with Metacello you can specify something like:
"take the last stable version known to work in trunk 4.2"
It could seem like an advantage.
But there is no magic, someone has to hardcode some version numbers somewhere.

The right question is whether we should maintain two different
versions of these informations (Metacello + trunk/Installer) or a
single one ?

Nicolas

> On Thu, Dec 9, 2010 at 4:13 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
>> Am 2010-12-09 um 10:17 schrieb Alexander Lazarević:
>>>
>>> You tell me. The benefit I see of just using installer is, that only one package gets installed. Using a Metacello Config I get all the Metacello mambo jumbo + Gofer + RoelTyper. I don't know if OCompletion benefits a great deal by having RoelTyper installed. Maybe someone else could answer this.
>>> And with installer it loads about eight times faster. So if OCompletion will not be an integrated part of 4.2, this seems to be a quick way to get it into such an image.
>>> One could see how complex the OCompletion installtion will be in the future and switch to a Metacello Config then, no?
>>>
>>
>> Actually, RoleTyper seems to be a requirement of
>> OCompletion.
>>  FWIW, The Metacello Config is meant to be Installable
>> at any future point in time, your installer Doit + the
>> two other doits may change. For example, if the developers
>> of OCompletion just put another _non-working_ version
>> into their repo, your doit will miraculously result in
>> a non-working OCompletion, while a Metacello-installation
>> would still work. Or consider a rename of the packages
>> from Ocompletion to OCompletion. The metacello-config
>> can immediately be updated, while the 'Extending the System'-
>> Workspace cannot as fast be updated.
>>
>> My rationale: Why shouldn't we use Metacello Configs if
>> they are there and doing what we want: Installing the
>> software.
>>
>> So Long,
>>        -Toibas
>>
>>
>>
>
>