Versionner and package dependencies
Locked
Versionner and package dependencies
 
|
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: #('EyeSee'). spec repository: 'http://smalltalkhub.com/mc/Moose/Glamour/main' ]. But in versionner I can only add a project as dependency. Is there a way to do such a thing or is it a future feature of versionner? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France |
signature.asc (836 bytes)
Re: Versionner and package dependencies
|
|
Hi Cyril,
Le 30 déc. 2015 à 10:17, Ferlicot D. Cyril a écrit :
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 create a project for that and then ask Versionner to only load the package you need (right-click on the project dependency). Christophe
|
Re: Versionner and package dependencies
|
|
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 create a project for that and then ask > Versionner to only load the package you need (right-click on the project > dependency). > > Christophe So we have to create ourself a configuration for each project that doesn't have a configuration/group that match our needs if we want to use versionner if I understand right. Ok, thank you. And is there a way to execute pre/post scripts (#postLoadDoIt: in ConfigurationOfXXX) with versionner ? If not is it something you want to add to versionner or this will not be add ? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France |
Re: Versionner and package dependencies
|
|
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 they have themselves >> dependencies. >> What you should do is to create a project for that and then ask >> Versionner to only load the package you need (right-click on the project >> dependency). >> >> Christophe > > Hi, > > So we have to create ourself a configuration for each project that > doesn't have a configuration/group that match our needs if we want to > use versionner if I understand right. Ok, thank you. > > And is there a way to execute pre/post scripts (#postLoadDoIt: in > ConfigurationOfXXX) with versionner ? If not is it something you want to > add to versionner or this will not be add ? It is Metacello that execute these scripts. Versionner only allows you to edit configurations. The load options in Versionner use Metacello, so they are executed. |
| Free forum by Nabble | Edit this page |