On May 22, 2014, at 5:00 AM, Christophe Demarey <christophe.dema...@inria.fr> 
wrote:

>> In general I am not so sure that adding configurations for one simple 
>> package are the way to go though. It seems like adding extra layers of 
>> indirection for reasons that are unclear to me.
> 
> The reason is that any package* should be self described. Your configuration 
> describes your project. If you use another piece of software, it should also 
> be self-described.
> Let's take the following example:
>       • for now, it's easy for you to add a direct dependency to 
> Roassal2Spec, just as if it was a part of your project ... => no problem
>       • ... but it is not. Maybe tomorrow, Alex will need to add a dependency 
> to one or more packages for Roassal2Spec => you will have problems because 
> you will not get these dependencies. Of course, you can still add them to 
> your configuration but you can easily see that you will end with a 
> configuration including all flatten dependencies, and with a lot of 
> dependencies not directly related to your project (transitive dependencies). 
> Flatten dependencies is really something that we should avoid, else 
> maintenance of dependencies will be a hell.
> That's why I'm really in favor of having configurations, even for one single 
> MC package inside the configuration.

I understand what you are saying, but my point of view is different. I put a 
high priority on the simplicity rule: if it is just one package with no special 
dependencies the Monticello package is the simplest solution, so you use that. 
If there are special dependencies, then the simplest solution for that package 
to work is to have a configuration for it, so you create it.

The latter is still not so obvious apparently, Alex has tried 2 times to 
include Roassal2Spec in the Roassal config, and it still does not load in a 
default Pharo 3. Alex, can you try again? ( hint hint :-) ) 

---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile


Reply via email to