dorsal team mailing list archive

[Harish Narayanan <harish.mlists@xxxxxxxxx>]

On 6/19/11 11:47 AM, Joachim Berdal Haga wrote:
> Hi Johan,
> 
> I haven't followed Dorsal in a while, but maybe I can still answer the
> question (if I understand it correctly).
> 
>> My thought was to either set PYTHONVER in the platform file and use
>> python.package and it would be smart enough to install the correct version,
>> defaults to 2.7, or use python2.X.package files and hardcode the version in
>> that way. The latter is easier, but then we need to set the PYTHONVER variable
>> in the python2.X.pacakge files. Do you do that with a simple export?
> 
> In general, variables set in .platform are to enable the packages to
> use the platform (yum/apt/etc) packages, e.g., to use the RHEL python.
> Variables set in .package are to enable the packages to use the
> dorsal-installed python instead.
> So (conceptually) this should go into the .package file.
> 
> Variables that are exported by "export" or "default" are visible to
> all packages LATER in the build, so python should probably be listed
> among the first ones. The difference between "export" and "default" is
> just that the later does not change the variable if already set by the
> user; in this case, "export" is probably correct since PYTHONVER may
> be set to a version we do not want to use (?).
> 
> So: Yes, you do that with a simple export :)

This is correct. An in addition, if you want to ensure that PYTHONVER
(or any other variable) is set even though a package may be 'skip:'ed
during installation, you define it as:

package_specific_register () {
    export foo=bar
    ...
}

Harish