Bug #2518

extra-requires in template

Added by J. Moringen about 7 years ago. Updated over 6 years ago.

Status:ClosedStart date:03/13/2016
Priority:NormalDue date:
Assignee:J. Moringen% Done:

0%

Category:Processing Model
Target version:0.7

Description

Original report: https://opensource.cit-ec.de/issues/474

ich habe mal ein paar issues in Form eines Beispiels gesammelt:
Die letzten 3 commits in https://opensource.cit-ec.de/projects/citk/repository?utf8=%E2%9C%93&rev=buildgen-bugs sind:

  • 6c46857 (variable-order) have extra-provides in template 29 minutes ago Robert Haschke
    Der Versuch für ein eigenes template die "provides" section direkt im template zu definieren, funktioniert zu halbwegs:
    - extra-provides kann nur in der general variable section definiert werden, anderswo wird es komplett ignoriert
    - Die Auflösung des ${version-name} funktioniert aus irgendwelchen Gründen nicht.

History

#1 Updated by J. Moringen about 7 years ago

- extra-provides kann nur in der general variable section definiert werden, anderswo wird es komplett ignoriert

Yes, extra-provides and extra-requries are project-level, not job-level, concepts. Is that a problem in your use-case?

- Die Auflösung des ${version-name} funktioniert aus irgendwelchen Gründen nicht.

I will investigate.

#2 Updated by R. Haschke about 7 years ago

- extra-provides kann nur in der general variable section definiert werden, anderswo wird es komplett ignoriert

Yes, extra-provides and extra-requries are project-level, not job-level, concepts. Is that a problem in your use-case?

I guess, that's fine. I just wanted to ensure, that the setting can't be overruled in the project itself.

#3 Updated by J. Moringen almost 7 years ago

  • Status changed from New to Feedback

- Die Auflösung des ${version-name} funktioniert aus irgendwelchen Gründen nicht.

I will investigate.

The problem is not ${version-name} but something else. In the example:

"extra-provides": [ [ "catkin", "${project-name}", "${version-name}" ],
                    [ "catkin", "${project-name}"                    ] ]

both elements are considered to be equal. That is, a project-version cannot currently require or provide multiple versions of a particular dependency.

The following works as expected:

"extra-provides": [ [ "catkin", "${project-name}", "${version-name}" ] ]

Note that this can satisfy both versioned and unversioned requirements, i.e. (assuming project-name = spread, version-name = 4.3) all the following

[ "catkin", "spread"        ]
[ "catkin", "spread", "4.3" ]
[ "catkin", "spread", "4.1" ]
[ "catkin", "spread", "2"   ]

but not

[ "catkin", "spread", "5"   ]
[ "catkin", "spread", "4.8" ]

#4 Updated by R. Haschke almost 7 years ago

Thanks. Works with removing the extra extra-provides entry.

#5 Updated by J. Moringen almost 7 years ago

  • Status changed from Feedback to Resolved

#6 Updated by J. Moringen over 6 years ago

  • Target version set to 0.8

#7 Updated by J. Moringen over 6 years ago

  • Status changed from Resolved to Closed
  • Target version changed from 0.8 to 0.7

Also available in: Atom PDF