diff options
| author | schmonz <schmonz> | 2002-12-26 04:12:49 +0000 |
|---|---|---|
| committer | schmonz <schmonz> | 2002-12-26 04:12:49 +0000 |
| commit | 023af0ff856da03a21124d3142891049d2d17037 (patch) | |
| tree | ff57310cf16b1c8b1009e9e1d6c7476cf208a354 /mk/buildlink2/buildlink2.txt | |
| parent | ca11a8f116b8e8cbeff909835ec0522520b4ad79 (diff) | |
| download | pkgsrc-023af0ff856da03a21124d3142891049d2d17037.tar.gz | |
buildlink1 is dead. Long live buildlink2! (Perhaps Q2 should be removed.)
Diffstat (limited to 'mk/buildlink2/buildlink2.txt')
| -rw-r--r-- | mk/buildlink2/buildlink2.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/mk/buildlink2/buildlink2.txt b/mk/buildlink2/buildlink2.txt index 21025a62272..16d982baa3e 100644 --- a/mk/buildlink2/buildlink2.txt +++ b/mk/buildlink2/buildlink2.txt @@ -1,7 +1,7 @@ -$NetBSD: buildlink2.txt,v 1.7 2002/12/25 05:16:12 schmonz Exp $ +$NetBSD: buildlink2.txt,v 1.8 2002/12/26 04:12:49 schmonz Exp $ The buildlink2 framework is a departure from the original buildlink -framework, which tries to do its work up-front before the configure +framework, which tried to do its work up-front before the configure process and fix things up after the build process. Over time, the buildlink framework grew overly complex to deal with software that stored build-time information in the installed files, e.g. GNOME packages. The @@ -28,7 +28,7 @@ To-do list: Here are some FAQs and answers regarding buildlink2: -Q1: Why is the buildlink2 framework better than the existing one? +Q1: Why is the buildlink2 framework better than the old one? A1: There are several reasons: (1) The new framework makes it simpler to buildinkify a package because @@ -59,7 +59,7 @@ A1: There are several reasons: process, so we don't accidentally trigger rebuilds of those files during the install process. -Q2: How does this affect packages that use the existing buildlink framework? +Q2: How does this affect packages that use the old buildlink framework? A2: The buildlink and buildlink2 frameworks can coexist within pkgsrc, but packages that use the new framework must use it exclusively, i.e. a package Makefile can't include both buildlink.mk and buildlink2.mk |