@pmatilai commented on this pull request.
> + * Upstream build scripts using tools like maker, cmake, ant, ...
+ * rpmbuild for running those via a Spec file
+ * Build systems for installing build dependencies and keeping track of build
artifacts
+ * Package repositories offering binary packages
+ * Installers/Updaters selecting and downloading packages
+ * rpm checking for consistency and installing/updating the packages
+
+As such RPM is only a part in a larger set of tools and some users may
+never actually interact with RPM directly.
+
+## Design goals
+
+* General purpose software management
+* Building from pristine sources
+* Unattended operation
+ * for both building
"for both building" doesn't make sense, looks like an editing leftover :)
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3299#pullrequestreview-2339866126
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/3299/review/2339866...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
