[Rpm-maint] [rpm-software-management/rpm] Document rpm design philosophy in the manual (Issue #2897)

[Panu Matilainen]

Max-rpm has a section on [philosophy](https://ftp.osuosl.org/pub/rpm/max-rpm/ch-rpm-philosophy.html) but it's a source one doesn't really want to link to because it's *soooo* outdated now. We should have a section explaining the fundamental design principles of rpm in our reference manual, many/most people probably don't even realize rpm *has* a philosophy.

This came up indirectly when somebody asked about interactivity in rpm (install) scriptlets. Somehow one of the most important aspects of rpm - the fact that by design all operations are unattended - doesn't seem to be mentioned *anywhere at all*. This is just tribal knowledge, those in the tribe just know, and those outside it, like the average 3rd party commercial vendor who wants to present an EULA for their software at install time... and we can' even point them to any canonical source of information as to why that's a total no-no. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2897
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2897 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240212/3797f543/attachment.html>