While anything would be better than the current situation, from a rpm user POW,
I'd like less magic and special things in rpm, and more generic operators and
constructs.
IE, everything is a variable, except for things that need multiple
declarations, and use tags.
SourceX as a tag is IMHO a mistake, for example. You'll never need to declare
it multiple time, since you need a unique name to attach special setup actions
to. So special tag + special operator does not improve things a lot.
Generic constructs help automating a lot, special constructs need special
handling, that always neem to hit corner cases.
So as a long term direction, I'd like unique name tags to be slowly deprecated
and replaced by unique name variables with generic variable set/unset behaviour.
And, for Tags that can not be converted to variables right now, because they
*need* the multiple declaration property, I’d like rpm to grow *generic*
multi-declaration primitives.
1. for Tags that are multi-declared as a poor man way to create arrays: add
real rpm variable arrays (`%set array [a,b,c]`, `%append array [d,e]`, `%array
%= [a,b,c]`, `%array %+= [d,e]`)
2. for Tags that multi-declared as part of a subpackage scope: create a real
`%{scope(subpackage): }` primitive (that’s just a generalisation of the `-n`
used by `%package`, `%description`, `%files`, etc, except without needing a
separate flag per line, and without all the bugs when you cut and paste and
forget to change the `-n` value on one of the lines)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/372#issuecomment-606542947_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
