> If you have lots of those with nothing but the name changing, no macros will
> help with that.
Since e.g. the `gem_libdir` is macro, it could instead of accepting the
parameter use some macro on background. So the question is can we have such
macro?
> Generate those files manifests programmatically from %install and include
> with %files -f. Or use dynamic spec generation to generate even those.
For me, the `%files` section is not about getting some random files into
package. If I greatly simplify the problem, the files section such as:
~~~
%files
%{_libdir}
~~~
is not the way to go and generated file list are very similar to this. While
they allow to include everything what is on file system, they don't cover my
back and they don't tell mi if e.g. soname has changed, if there are new files,
which need review or if some files gone missing.
But maybe I just like doing things the hard way 🤷
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2876#discussioncomment-8244926
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/2876/comments/8244...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
