This is a multipart message in MIME format.
--=_alternative 0066D02185257122_=
Content-Type: text/plain; charset="us-ascii"

Hi pkgsrc-users:

Posing my experiences with security/beecrypt for your info and feedback 
.. here goes:

I have run into a problem building security/beecrypt in pkgsrg.
My host is Red Hat Linux Enterprise Workstation Release 3 Update 6
My pkgsrc metadata is as of 2006-02-19.

Basically, when beecrypt builds its python bindings, its configure script 
finds "python" on the path, and queries this python for include and lib 
paths.  This is done with no knowledge whatsoever of all the nifty data 
provided by pkgsrc's lang/python/pyversion.mk.

In my case, I have built python2.4 in pkgsrc, but my system has python2.2 
in /usr/bin/python.  Since beecrypt's configure has no knowledge of the 
info pyversion.mk provides, it finds /usr/bin/python, and tries to install 
the bindings to /usr/lib/python2.2/* which I don't have permission to 
install to.

I fixed this problem (for me) by the following:
1) in lang/python24/Makefile, add post-install target as follows:
post-install:
        ${LN} -fs ${PREFIX}/bin/python2.4 python
so that pkgsrc's python2.4 is found via the generic name "python" in my 
pkgsrc bin dir

and

2) In security/beecrypt/Makefile, add:
#include "../../lang/python/pyversion.mk"
so that the wrapper phase sets up the .buildlink stuff for python.

I'm sure this isn't the _right_way_ to fix it ... it seems to me that 
beecrypt's configure needs to be made pkgsrc aware.

FYI,
Tim Noell
Lexmark International, Inc.

--=_alternative 0066D02185257122_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hi pkgsrc-users:</font>
<br>
<br><font size=2 face="sans-serif">Posing my experiences with security/beecrypt for your info and feedback ... here goes:</font>
<br>
<br><font size=2 face="sans-serif">I have run into a problem building security/beecrypt in pkgsrg.</font>
<br><font size=2 face="sans-serif">My host is Red Hat Linux Enterprise Workstation Release 3 Update 6</font>
<br><font size=2 face="sans-serif">My pkgsrc metadata is as of 2006-02-19.</font>
<br>
<br><font size=2 face="sans-serif">Basically, when beecrypt builds its python bindings, its configure script finds &quot;python&quot; on the path, and queries this python for include and lib paths. &nbsp;This is done with no knowledge whatsoever of all the nifty data provided by pkgsrc's lang/python/pyversion.mk.</font>
<br>
<br><font size=2 face="sans-serif">In my case, I have built python2.4 in pkgsrc, but my system has python2.2 in /usr/bin/python. &nbsp;Since beecrypt's configure has no knowledge of the info pyversion.mk provides, it finds /usr/bin/python, and tries to install the bindings to /usr/lib/python2.2/* which I don't have permission to install to.</font>
<br>
<br><font size=2 face="sans-serif">I fixed this problem (for me) by the following:</font>
<br><font size=2 face="sans-serif">1) in lang/python24/Makefile, add post-install target as follows:</font>
<br><font size=2 face="sans-serif">post-install:</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; ${LN} -fs ${PREFIX}/bin/python2.4 python</font>
<br><font size=2 face="sans-serif">so that pkgsrc's python2.4 is found via the generic name &quot;python&quot; in my pkgsrc bin dir</font>
<br>
<br><font size=2 face="sans-serif">and</font>
<br>
<br><font size=2 face="sans-serif">2) In security/beecrypt/Makefile, add:</font>
<br><font size=2 face="sans-serif">#include &quot;../../lang/python/pyversion.mk&quot;</font>
<br><font size=2 face="sans-serif">so that the wrapper phase sets up the .buildlink stuff for python.</font>
<br>
<br><font size=2 face="sans-serif">I'm sure this isn't the _right_way_ to fix it ... it seems to me that beecrypt's configure needs to be made pkgsrc aware.</font>
<br>
<br><font size=2 face="sans-serif">FYI,</font>
<br><font size=2 face="sans-serif">Tim Noell</font>
<br><font size=2 face="sans-serif">Lexmark International, Inc.</font>
<br>
--=_alternative 0066D02185257122_=--