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

[nim-nim]

> > Can it be fixed to expand on use? That’s the useful functional place to do it.
> 
> It's still effectively on the first use, the gotcha is that the first use is actually by rpm itself right

That’s 100% uninteresting for rpm users, because that make specs depend on internal ill documented rpm artefacts, and effectively makes this internal behaviour a public API (with all the constrains of a public API, and the usual conflicts whenever rpm devs will attempt changing this API). 

-- 
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-610887954
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20200408/ce03aae6/attachment.html>