On 11/9/06, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: Stephane Bailliez [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 09, 2006 8:43 AM > To: [email protected] > Subject: Re: infallibility-of-metadata would be better from this point > > I would not really look for granular metadata revision to the > node level (this can get too complicated and is really > unecessary to me) but more on the whole repository thing. > Basically on your configuration you would say "I depend on > r214093 of the repository (or a tag name if you wish...)) > I fear it would be too simple. When we talk about a build being reproduceable, most of the time it doesn't meant relaunch exactly the same build. Most of the time, it actually means "change a few things and be sure that all the rest is excactly the same". With a single release number of the repository, it would be hard to say "change only the metadata of one specific dependency". Moreover, ivy support the simultaneous usage of multiple repository. You will thus need more than one release number of the repository.
Another problem I see is that if on one hand there is a module for which the latest metadata correspond to what you want but on the other hand for anotherr module you need an old version, then no repository version is really good. I would be more in favor of a version number for each file stored in a
repository. And when we prepare a release, the resolved version number of the meta-data should be stored similarily to the resolved version numbers of the jars.
This is also what I think can address the more use cases, but where I agree with Stephane is that it may soon become very complex. So maybe we should try to identify use cases and compare the solutions we foresee. A wiki would really be great for that, I'm already getting a bit lost in what everybody think, so I guess that somebody missing a few days will be in trouble to capture the ideas behind all the mails. Xavier Gilles
