Le 04/01/2016 10:44, Christophe Demarey a écrit :
> Hi Cyril,
>
> It is not something we want in Versionner.
> An external project *must* have a configuration to refer to it. If not,
> you will take random packages without knowing if they have themselves
> dependencies.
> What you should do is to
Hi Cyril,
Le 30 déc. 2015 à 10:17, Ferlicot D. Cyril a écrit :
> Hi,
>
> I wanted to use versionner to manage some existing configurations but in
> one of these configuration there is some dependencies on packages that
> have no project.
>
> For example in the baseline there is:
>
>
Le 4 janv. 2016 à 10:52, Ferlicot D. Cyril a écrit :
> Le 04/01/2016 10:44, Christophe Demarey a écrit :
>> Hi Cyril,
>>
>> It is not something we want in Versionner.
>> An external project *must* have a configuration to refer to it. If not,
>> you will take random packages without knowing if
Hi,
I wanted to use versionner to manage some existing configurations but in
one of these configuration there is some dependencies on packages that
have no project.
For example in the baseline there is:
spec package: 'Glamour-EyeSee-Presentations'
with: [ spec requires:
