On Mon, Aug 29, 2016 at 10:52 AM, Nicolas Passerini <[email protected]> wrote: > Well, I am not sure if this has to do with Iceberg itself, because Iceberg > does nothing with dependencies. > > But I am not sure that a ConfigurationOfXXX really has information of only > one package. Normally you will have only one configuration for each project, > am I wrong? > Then the configuration specifies (among other stuff) dependencies between > the parts (packages) of your project... I think this is right. > If you depend in another project, then you should not depend in specific > packages but in another configuration.
With the Iceberg tool, you can load or unload packages. How it will works if the dependencies are not loaded before ? > The problem here is that we are (at least Iceberg is) assuming a correlation > between project and repository, because in fact Iceberg handles > repositories. If a project would be spawn in several repositories, at least > now Iceberg can't do anything about it, it will treat them as independent > "projects". I am not sure about changing this logic in the near future, and > also we should think if that is not a Cargo/Metacello feature. I never see a project spawn on many repo. I guess you can safely say that 1 project = 1 repo. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/
