It probably depends on the order the variables are set... That can be useful while the max length of an environment variable value is 255. Maybe that's something to think of, for the future... :-) Thank you Emmanuel
-----Message d'origine----- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 avril 2008 17:21 À : [email protected] Objet : Re: Environment variable resolution I'd say yes but I never tested it. Emmanuel On Wed, Apr 9, 2008 at 2:53 PM, benoit LUTTRINGER < [EMAIL PROTECTED]> wrote: > Ok, so my SVN_HOME/bin has to be in the PATH anyway. > > But now let's say that I define the A environment variable (value : > "aaa"), and then the B environment variable which value is "$A:bbb". > Will the value of B finally be "aaa:bbb" during the build? > > > -----Message d'origine----- > De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 9 avril 2008 14:43 > À : [email protected] > Objet : Re: Environment variable resolution > > Installations are used only for the build part and not for the scm > actions, > so you SVN_HOME won't be used except if you use it in your build. > > Emmanuel > > On Wed, Apr 9, 2008 at 1:41 PM, benoit LUTTRINGER < > [EMAIL PROTECTED]> wrote: > > > Hi all, > > > > > > > > Is this possible that Continuum resolves environment variables ? > > > > For instance, let's say I define the SVN_HOME variable through > > continuum, using 'Installations'>'Environment variable'. > > > > Then, using the same mean, I create the environment variable PATH which > > value is < $PATH : $SVN_HOME/bin > (I work under Linux). > > > > > > > > Will the PATH variable be created and resolved correctly ? > > > > I suppose not but who knows ? :-) > > > > I see there must be a problem regarding the order in which the continuum > > application declares environment variables at the process's beginning. > > > > > > > > If this is not possible yet, maybe it would be a great enhancement for > > the future. > > > > > > > > Thanks for your answers. > > > > > > > > Benoit > > > > >
