Current approach of changelog generation (baked into spec template) isn't suitable for DUPs that have several releases, as spec has to be adjusted manually after its generation. So, the proposed way to handle this is the following:
- Store changelog in a separate file
- Update it on each spec generation if package's NVR has been changed
- Include changelog file contents in the resulting spec during the spec generation
Current approach of changelog generation (baked into spec template) isn't suitable for DUPs that have several releases, as spec has to be adjusted manually after its generation. So, the proposed way to handle this is the following: