Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine how package attributes/files might be templated using package metadata #210

Closed
nacl opened this issue Aug 3, 2020 · 2 comments
Labels
P3 An issue that we are not working on but will review quarterly

Comments

@nacl
Copy link
Collaborator

nacl commented Aug 3, 2020

It was pointed out in the review for #173 that we may want to expand various template attributes (e.g. the version) to other parts of the RPM spec file, such as the %description.

This raises another larger point: what attributes of packages should be template-able? In many cases, it might make sense to subject all of them to template substitution, for example, some filesystem paths are annotated with versions, like those in /usr/share/doc in CentOS.

Another important part of this is figuring out the templates' syntax and how they're to be processed in a cross-platform manner.

@aiuto
Copy link
Collaborator

aiuto commented Aug 14, 2020

Yes. The more the merrier. The idea in #198 allows us to bring a dict of string->string mappings into any of the rules so that we can expand it in any way we need. Any rpm spec template is a possibility

@aiuto aiuto added the P3 An issue that we are not working on but will review quarterly label May 3, 2021
@aiuto
Copy link
Collaborator

aiuto commented Apr 16, 2024

This is getting old and not specifically actionable. Closing to clean out the backlog.

@aiuto aiuto closed this as completed Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 An issue that we are not working on but will review quarterly
Projects
None yet
Development

No branches or pull requests

2 participants