AFAICS the command appstreamcli news-to-metainfo --limit=2 NEWS METAINFO.in METAINFO.xml parses the whole NEWS file and then uses only the information retrieved in the latest two release entries to copy them in the metainfo file.
As a result, when you try to introduce this script in a project with a long history and a long NEWS file (not compliant with the format appstreamcli expects to find), it seems the best solution is moving the old NEWS to NEWS.old and then write a new NEWS file from scratch. Fixing all the old release entries is not worth the effort.
I'm wondering if my analysis is correct or if I'm missing something.
What if --limit may be adjusted to parse only the first N occurencies of Version in the NEWS file so we can fix the format of the latest releases only and keep the history in a single file?
The text was updated successfully, but these errors were encountered:
AFAICS the command
appstreamcli news-to-metainfo --limit=2 NEWS METAINFO.in METAINFO.xmlparses the whole NEWS file and then uses only the information retrieved in the latest two release entries to copy them in the metainfo file.As a result, when you try to introduce this script in a project with a long history and a long NEWS file (not compliant with the format appstreamcli expects to find), it seems the best solution is moving the old NEWS to NEWS.old and then write a new NEWS file from scratch. Fixing all the old release entries is not worth the effort.
I'm wondering if my analysis is correct or if I'm missing something.
What if
--limitmay be adjusted to parse only the first N occurencies ofVersionin the NEWS file so we can fix the format of the latest releases only and keep the history in a single file?The text was updated successfully, but these errors were encountered: