[Rpm-maint] [rpm-software-management/rpm] Discussion: spec tag order and side-effects (#1161)

[nim-nim]

As i said in the rhbz issue, no problem adapting existing specs and guidelines to some new ordering, as long as this ordering is clearly defined and rpm upstream commits to it.

However, I am completely opposed to changing things that worked in the previous undefined space, to something that works today but is still in the undefined space and may break from one day to the next as a side effect of rpm code changes.

Right now, I'm seing rpm upstream moving dirt from one carpet part to another, without committing to anything, while asking rpm users to do a lot of work to adapt to this dirt move.

-- 
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/1161#issuecomment-610264062
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20200407/7ca5c8d9/attachment.html>