From cc6b1b76a7a96807acf37a1d18d1f3e45a24baaa Mon Sep 17 00:00:00 2001 From: rillig Date: Sat, 7 Oct 2006 09:31:16 +0000 Subject: Stated some major goals of pkgsrc: - high quality of the generated packages - platform independence, portability - uniform look and feel on all platforms Feel free to add you own goals. --- doc/guide/files/introduction.xml | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/doc/guide/files/introduction.xml b/doc/guide/files/introduction.xml index 1d49d376a99..746764f1cb5 100644 --- a/doc/guide/files/introduction.xml +++ b/doc/guide/files/introduction.xml @@ -1,4 +1,4 @@ - + What is pkgsrc? @@ -81,6 +81,27 @@ pkgsrc provides the following key features: available right out of the box, so you can configure it specifically for your environment. + +The following principles are basic to pkgsrc: + + + +It should only work if it's right. +— That means, if a package contains bugs, it's better to find +them and to complain about them rather than to just install the package +and hope that it works. There are numerous checks in pkgsrc that try to +find such bugs: Static analysis tools (pkgtools/pkglint), build-time checks (portability +of shell scripts), and post-installation checks (installed files, +references to shared libraries, script interpreters). + +If it works, it should work everywhere +— Like NetBSD has been ported to many hardware architectures, +pkgsrc has been ported to many operating systems. Care is taken that +packages behave the same on all platforms. + + + -- cgit v1.2.3