Re: Trouble with math/lp_solve buildlink

[Francois Tigeot <ftigeot%wolfpond.org@localhost>]

On Sun, May 08, 2011 at 06:48:17PM +0200, Thomas Klausner wrote:
> On Sun, May 08, 2011 at 02:21:33PM +0200, Francois Tigeot wrote:
> 
> > Chapter 10 says "If the buildlink3.mk file does not exist, add a DEPENDS 
> > line to the Makefile".
> 
> Usually all packages with libraries already have a buildlink3.mk file;
> in that case the advice is good, because you don't need a
> buildlink3.mk file for binaries.
> 
> For this case, it was wrong

Documentation patch attached for review ;)

I'm not too sure of all the pre-requisites, so I prefer to send it to the
list first.

-- 
Francois Tigeot

? patch-doc_guide.txt
? files/.creating.xml.swp
Index: files/creating.xml
===================================================================
RCS file: /cvsroot/pkgsrc/doc/guide/files/creating.xml,v
retrieving revision 1.9
diff -u -u -r1.9 creating.xml
--- files/creating.xml  7 Sep 2009 18:22:10 -0000       1.9
+++ files/creating.xml  16 May 2011 19:21:11 -0000
@@ -35,11 +35,14 @@
 file called <filename>buildlink3.mk</filename> in that directory, add a
 line to your package <filename>Makefile</filename> which includes that
 file just before the last line. If the
-<filename>buildlink3.mk</filename> file does not exist, add a
-<varname>DEPENDS</varname> line to the Makefile, which specifies the
-version of the dependency and where it can be found in pkgsrc. This line
-should be placed in the third paragraph. If the dependency is only
-needed for building the package, but not when using it, use
+<filename>buildlink3.mk</filename> file does not exist, it must be
+created first..
+
+You can add a <varname>DEPENDS</varname> line to the Makefile, which
+specifies the version of the dependency and where it can be found in
+pkgsrc. This line should be placed in the third paragraph. If the
+dependency is only needed for building the package, but not when using
+it, use
 <varname>BUILD_DEPENDS</varname> instead of <varname>DEPENDS</varname>.
 Your package may then look like this:</para>
 
@@ -54,6 +57,7 @@
 
 .include 
"../../<replaceable>category</replaceable>/<replaceable>package</replaceable>/buildlink3.mk"
 .include "../../devel/glib2/buildlink3.mk"
+.include "../../misc/screen/buildlink3.mk"
 .include "../../mk/bsd.pkg.mk"
 </programlisting>
 
Index: files/fixes.xml
===================================================================
RCS file: /cvsroot/pkgsrc/doc/guide/files/fixes.xml,v
retrieving revision 1.103
diff -u -u -r1.103 fixes.xml
--- files/fixes.xml     16 Jan 2011 08:40:28 -0000      1.103
+++ files/fixes.xml     16 May 2011 19:21:12 -0000
@@ -341,13 +341,22 @@
 
        <para>If your package needs a library with which to link and
        again there is no <filename>buildlink3.mk</filename> file
-       available, this is specified using the
-       <varname>DEPENDS</varname> definition. For example:</para>
+       available, you have to create it first.</para>
+       
+       <para>The <varname>DEPENDS</varname> definition can be used
+       to specify that a package will only build against a certain
+       minimum version of a pre-requisite:</para>
 
        <programlisting>
-DEPENDS+=       xpm-3.4j:../../graphics/xpm
+DEPENDS+=       tiff>=3.5.4:../../graphics/tiff
        </programlisting>
 
+       <para>This means that the package will build against version
+       3.5.4 of the tiff library or newer.  Such a dependency may
+       be warranted if, for example, the API of the library has
+       changed with version 3.5.4 and a package would not compile
+       against an earlier version of tiff.</para>
+
        <para>You can also use wildcards in package dependencies:</para>
 
        <programlisting>
@@ -365,20 +374,6 @@
        such as <quote>tk-postgresql</quote> matching a
        <quote>tk-*</quote> <varname>DEPENDS</varname>.</para>
 
-       <para>Wildcards can also be used to specify that a package
-       will only build against a certain minimum version of a
-       pre-requisite:</para>
-
-       <programlisting>
-DEPENDS+=       tiff>=3.5.4:../../graphics/tiff
-       </programlisting>
-
-       <para>This means that the package will build against version
-       3.5.4 of the tiff library or newer.  Such a dependency may
-       be warranted if, for example, the API of the library has
-       changed with version 3.5.4 and a package would not compile
-       against an earlier version of tiff.</para>
-
        <para>Please note that such dependencies should only be
        updated if a package requires a newer pre-requisite, but
        not to denote recommendations such as

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay

_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss