summaryrefslogtreecommitdiff
path: root/mk
diff options
context:
space:
mode:
authorjlam <jlam>2003-09-09 09:13:20 +0000
committerjlam <jlam>2003-09-09 09:13:20 +0000
commit2336478bd10bc2738a886f8210dfb713bac063f9 (patch)
tree329f3c75313a32db09e69dfd18e939ebf54118f5 /mk
parent6bb7eff9da1191f2434844dac7e8178428b55c5e (diff)
downloadpkgsrc-2336478bd10bc2738a886f8210dfb713bac063f9.tar.gz
Note how package views is also similar to GNU Stow, but state clearly the
main difference in philosophy between package views and these other software management systems.
Diffstat (limited to 'mk')
-rw-r--r--mk/buildlink3/README18
1 files changed, 12 insertions, 6 deletions
diff --git a/mk/buildlink3/README b/mk/buildlink3/README
index 8eeef91f4aa..19699c9283c 100644
--- a/mk/buildlink3/README
+++ b/mk/buildlink3/README
@@ -1,4 +1,4 @@
-$NetBSD: README,v 1.3 2003/09/08 10:36:02 jlam Exp $
+$NetBSD: README,v 1.4 2003/09/09 09:13:20 jlam Exp $
0 Package Views
===============
@@ -12,12 +12,18 @@ different views by appropriately setting shell environment variables,
e.g., PATH, MANPATH, etc.
Package views is similar in spirit to the Encap Package Management
-System and to the Carnegie Mellon University Depot Configuration
-Management system:
+System, the GNU Stow Project, and the Carnegie Mellon University Depot
+Configuration Management system:
http://www.encap.org/
+ http://www.gnu.org/software/stow/stow.html
http://asg.web.cmu.edu/andrew2/depot/
+However, these projects have a philosophy of "install anywhere, use in
+one place", whereas package views departs from that model with a
+philosophy that can roughly be summarized as "install in one place,
+use anywhere".
+
0.1 A short history of package views
====================================
@@ -37,8 +43,8 @@ work into the main pkgsrc branch. The code he developed languished on
the "pkgviews" branch for over a year, and in the meantime much code
was added to pkgsrc that increased the complexity and the capabilities
of pkgsrc, including buildlink2, which conflicted with Alistair's
-implementation of package views. In July 2003, Johnny Lam attempted
-to integrate the functionality on the pkgviews branch into modern
+implementation of package views. In September 2003, Johnny Lam
+integrated the functionality on the pkgviews branch into modern
pkgsrc. As part of the integration, a new buildlink3 framework was
created so that the the ability to isolate builds from differences in
the environment wouldn't be lost.
@@ -88,7 +94,7 @@ migrating their package system over to using pkgviews. The default,
Some highlight of pkgviews packages include:
* fully dynamic PLISTs
- * multiple version of the same package can co-exist
+ * multiple versions of the same package can co-exist
0.4 buildlink3 pkgsrc build framework