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

[Florian Festi]

List of things to talk about:

- Upstream tarball + patches to see what are the packager's changes
- SRPM has all needed to rebuild the package on its "home" distributing - assuming the distribution ships all (devel and tooling) packages
  - nosource as an exception 
- Optimized for updates - especially quick security updates
  - Package name as a line of updates instead of one time packaging (obsoletes as name change or split/merge)
  - Unattended updates
- Handle full life cycle of all owned files - but ignore all other files
- Scriptlets are supported but should be used very sparingly.
  - Most things can be done with file trigger only
    - E.g. register stuff in centralized catalogs, update caches  
  - Do all that can be done during build! Compiling and copying unowned files around is frowned upon!

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

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