Bug #2655: Variables defined on cmdline or in distribution-context cannot be used in versions section. - Automated Build Generator - Open Source Collaboration Platform

Bug #2655

Variables defined on cmdline or in distribution-context cannot be used in versions section.

Added by R. Haschke over 7 years ago. Updated about 7 years ago.

Status:

Feedback

Start date:

09/09/2016

Priority:

Normal

Due date:

Assignee:

% Done:

Category:

Processing Model

Target version:

1.0

Description

I would like to use the variable ${ros} to specify some versions of projects/recipes.

History

#1 Updated by J. Moringen over 7 years ago

Category set to Processing Model
Status changed from New to Feedback

R. Haschke wrote:

I would like to use the variable ${ros} to specify some versions of projects/recipes.

Please provide an example or test case.

#2 Updated by J. Moringen over 7 years ago

Subject changed from variables defined on cmdline or in distribution-context cannot be used in versions section. to Variables defined on cmdline or in distribution-context cannot be used in versions section.

#3 Updated by R. Haschke over 7 years ago

I used the following snippet:

    "variables": {
        "ros":                "${next-value|indigo}" 
    },

    "versions":  [
        [ "ni-arm-server-ros",     "${ros}"   ]
    ]

build-gen complains that version ${ros} is not available in ni-arm-server-ros.

#4 Updated by J. Moringen over 7 years ago

R. Haschke wrote:

I used the following snippet:

[...]

build-gen complains that version ${ros} is not available in ni-arm-server-ros.

I see. In the current architecture, repository URLs, version names and project references in distributions are not subject to variable expansion.

Do you absolutely need this now? I'm working on grafting the new frontend and data model onto the current generator. Hopefully, that will provide some of the benefits of the new architecture in the not-too-distant future.