action #56525

Create rpm requires from cpanfile

Added by coolo 7 months ago. Updated 1 day ago.

Status:In ProgressStart date:06/09/2019
Priority:NormalDue date:
Assignee:tinita% Done:

0%

Category:Organisational
Target version:Current Sprint
Difficulty:medium
Duration:

Description

Motivation

The cpanfile provides already perl dependencies and we should make use of it as good as we can to avoid duplication in the spec file

Acceptance criteria

  • AC1: Less duplication in dependencies
  • AC2: perl dependencies need to be specified manually in either cpanfile or .spec file, not both

Suggestions


Related issues

Blocks openQA Project - action #53546: Easier dependencies handling for packages, e.g. reduce du... Blocked 27/06/2019

History

#1 Updated by okurz 6 months ago

  • Blocks action #53546: Easier dependencies handling for packages, e.g. reduce duplication of build requirements in spec, documentation, Dockerfile added

#2 Updated by coolo 5 months ago

not started, just blocking

#3 Updated by okurz about 1 month ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Assignee deleted (coolo)

Apparently you have no capacity to pick this up.

Updated description with "Motivation", "Acceptance criteria", "Suggestions

#4 Updated by cdywan 1 day ago

  • Target version changed from Current Sprint to Ready

#5 Updated by okurz 1 day ago

  • Target version changed from Ready to Current Sprint

#6 Updated by tinita 1 day ago

How about creating a YAML or JSON file for the requirements and generate cpanfile and rpm from that?

Seems easier especially regarding dependencies per component. Not sure if that is actually possible with the cpanfile format.

Also cpanfile-dump doesn't support module versions, at least cpanfile-dump --help doesn't show anything regarding that.

#7 Updated by tinita 1 day ago

  • Status changed from Workable to In Progress
  • Assignee set to tinita

Also available in: Atom PDF