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.

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.��

On Sat, Aug 27, 2016 at 10:35 AM, Peter Uhnak <i.uhnak@gmail.com> wrote:

Hi,

one thing that I wanted to ask about IceBerg --- during the IceBerg talk Nico mentioned that we need to think in terms of projects.

Now I understand that perspective, because that's how git behaves and that's how _I_ think,

however at the same time, there is a strong push for focusing on packages... having each package describing it's dependencies, etc.

So my question is, how do those two views interact with each other? Because I feel like they are going against each other.

Peter