Ticket #45616

generate_metainfos.sh

Open Date: 2022-09-09 13:21 Last Update: 2022-10-28 19:05

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
6

Details

Let's move .metainfo.xml.in -> .metainfo.xml generation out from configure, to a separate script.

- It's easier to adjust such a script for future .xml.in -> .xml conversion needs than configure substitutions (this is why I think we will likely need this even to S3_0, and certainly to S3_1)
- Also meson based build can use such a common script

Ticket History (3/14 Histories)

2022-09-09 13:21 Updated by: cazfi
  • New Ticket "generate_metainfo.sh" created
2022-09-09 15:12 Updated by: cazfi
2022-10-08 07:24 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Resolution Update from None to Accepted
  • Summary Updated
2022-10-08 22:32 Updated by: cazfi
Comment

Reply To cazfi

- Also meson based build can use such a common script

-> #44095

2022-10-12 13:04 Updated by: cazfi
  • Resolution Update from Accepted to None
Comment

'make dist' from a test branch with this patch is failing with an error message indicating metainfo.xml files to blame.

2022-10-12 19:58 Updated by: cazfi
Comment

Reply To cazfi

'make dist' from a test branch with this patch is failing with an error message indicating metainfo.xml files to blame.

Let's start by implementing #45840, which should make proper implementation of this one much easier.

2022-10-22 09:46 Updated by: cazfi
  • Resolution Update from None to Accepted
Comment

Not much of the previous version remains - no point to list changes. It makes more sense to consider this as a new implementation.

2022-10-28 19:05 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

Please login to add comment to this ticket » Login