backup files included in packages are nothing but a result of faulty packaging,
where disablingdefault non-intrusive functionality of use are clearly not the
right solution and really should be considered flawed packaging practices and
workarounds rather than correctly addressing and fixing the issue, a matter
applied to software development in general.
Prevention of this should already be ensured through rpmlint checks, where
graded as error by default IIRC.
Further on, the truly proper, automatic and guaranteed prevention of this to
even be possible is through brp-* scripts run at end of %install.
For cooker we have an almost two decades old spec-helper package with
additional scripts to ensure packaging sanity, which I've over the past years
have implemented even further extensive scripts, while cleaning them up (ie.
such as spaghetti perl scripts difficult to maintain and read have been
rewritten in shell scripts easy to understand and maintain), which now really
is in a shape where not having pushed upstream earlier is almost an outrage..
:p
I will create a branch with these commited to soon and create a pull request
for.
FWIW: We've *never* actually experienced this as an actual problem in cooker..
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/109#issuecomment-266466153
_______________________________________________
Rpm-maint mailing list
[email protected]
http://lists.rpm.org/mailman/listinfo/rpm-maint
