Re: Feasibility of splitting out web components of lang/php5
06.01.2012 06:20, Doug Barton wrote: I do package build systems that support a variety of types of end systems. (Nearly) all of them use php in some form or another, but a substantial portion of them don't have web servers, and therefore don't need the cgi, apache module, or the apache dependency that comes with them. What would make my life a whole lot simpler is if lang/php5 were the command line version, and the cgi and apache modules were separate ports. Is this feasible? Long long ago when I was building php on linux by hand I noticed that cgi/apache/standalone binaries differ only in small subset of linker objects i.e. splitting this into many ports will made us for sure recompile whole php for each of them. So: * this is good from the installation perspective, when user can select which packages to install and have the components he really needs; * this is boring from the update perspective for those who build php by hand. I'd say that both options would be good to have. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: How to handle config files
On 01/08/2012 04:59, Martin Kropfinger wrote: Hi there! The porters handbook describes a way to handle config files: http://www.freebsd.org/doc/en/books/porters-handbook/plist-config.html It is recommended to do it this way for keeping changed files after deinstallation on the system. But the example is not really clear to me. What does this line do: @exec if [ ! -f %D/etc/orbit.conf ] ; then cp -p %D/%F %B/orbit.conf; fi Nothing is said about those variables... %D (which seems to be %%PREFIX%%) and %F or %B. Can anyone give me some help? I added a reference to pkg_create in that section, and tried to improve the wording a bit to make it more clear what the right course of action is. It should be on line in a few hours (assuming I didn't break the doc build again) please let me know if it helps you understand things better. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 9 Jan 2012 06:01, Da Rock freebsd-po...@herveybayaustralia.com.au
wrote:
All arguments aside, I've finally made headway - I think... its really
frustrating for me because to me it seems a bit of a blackbox atm. I'm
still trying to untangle the threads.
I fiddled and tweaked and finally got make to run. I then ran make
-DPACKAGE_BUILD makesum and got a checksum (SHA256 too). All the while I
had portlint run every now and again spitting out errors I couldn't quite
translate. After makesum I ran it again and it said looks fine. - I
called have slapped it silly! :) Bloody pretentious snot... could've been
more helpful earlier
I just need to work out how to check the checksum against a linux source.
I haven't found that yet.
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/\
http://herveybayaustralia.com.au/ports/distfiles/
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*
fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap \
usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.include bsd.port.mk
I'm cutting it to the bone as much as I can. But I am also trying to cut
some of the files that are unnecessary and could be risky. After running
make the directory looks like this:
./
./Makefile
./pkg-descr
./work
./work/etc
./work/etc/ldap.conf
./work/lib
./work/lib/security
./work/lib/security/pam_ldap.so
./work/usr
./work/usr/lib
./work/usr/lib/libnss_ldap-264.so
./work/usr/lib/libnss_ldap.so
./work/usr/lib/libnss_ldap.so.2
./work/usr/share
./work/usr/share/doc
./work/usr/share/doc/nss_ldap-264
./work/usr/share/doc/nss_ldap-264/ANNOUNCE.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.nss_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.pam_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.nss_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.nss_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.pam_ldap
./work/usr/share/doc/nss_ldap-264/README.TLS
./work/usr/share/doc/nss_ldap-264/README.nss_ldap
./work/usr/share/doc/nss_ldap-264/README.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.nss_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldapns.schema
./work/usr/share/doc/nss_ldap-264/ns-pwd-policy.schema
./work/usr/share/doc/nss_ldap-264/nsswitch.ldap
./work/usr/share/doc/nss_ldap-264/pam.d
./work/usr/share/doc/nss_ldap-264/pam.d/chfn
./work/usr/share/doc/nss_ldap-264/pam.d/chsh
./work/usr/share/doc/nss_ldap-264/pam.d/ftp
./work/usr/share/doc/nss_ldap-264/pam.d/gdm
./work/usr/share/doc/nss_ldap-264/pam.d/halt
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/163952[maintainer-update] games/pokerth: update to 0.9 o ports/163946[MAINTAINER] databases/php5-pdo_cassandra: fix build w f ports/163942[patch] fix i386 build of dns/inadyn o ports/163941proftpd compile failure with mod_shaper f ports/163940[update] ftp/vsftpd-ext 2.3.5 o ports/163939[MAINTAINER] x11-wm/ctwm: Patch potential amd64 issue f ports/163933Update security/zenmap to same vers as nmap o ports/163917[new port]: graphics/qmetro Map of the transport syste o ports/163914[MAINTAINER] lang/gnat-aux: Upgrade to gcc-4.6.2, add f ports/163910[update] chinese/ibus-chewing 1.3.10 o ports/163909[MAINTAINER-UPDATE][PATCH] please update math/lapacke o ports/163902[new port]: graphics/easypaint Easy graphic editing pr o ports/163897[NEW PORT] sysutils/dstat: A versatile resource statis o ports/163886New port: net/drawterm Plan9 cpu client o ports/163883[maintainer update] chinese/ibus-pinyin: update to 1.4 o ports/163882portupgrade of archivers/unrar-iconv has wrong patch o ports/163872devel/ioncube and distfiles o ports/163861new port: devel/art A Resource Tracer (A resource trac o ports/163850New port: cad/linux-bricscad f ports/163842[PATCH] www/xxxterm: update to 1.10.0 f ports/163818[MAINTAINER] textproc/simplehtmldom: update to 1.5 o ports/163806New port: devel/arduino-lib-irremote: A Multi-Protocol f ports/163800net-mgmt/nagiosql: All files are Windows-converted o ports/163796[maintainer update] update multimedia/xbmc to 11.0 bet o ports/163795New Port: www rubygems/url-mount Glue to allow mounted f ports/163766multimedia/openshot fails to find main and gtk mod f ports/163734[patch] dns/ldns -- options settings not functional f ports/163721[patch update] multimedia/libbluray 0.2.20110219 - 0. f ports/163714net/nss_ldap 1.265_7 does not return the full list of o ports/163712[PATCH] devel/ace attempts to cast const pointer to no f ports/163627mail/rss2email crash after py-html2text upgraded to 3. o ports/163616[new port] games/quadra: A tetris like multiuser actio o ports/163583[patch] x11/kdelibs3 conflicts with openssl-1 f ports/163510FreeBSD Port emulators/fceux Patch o ports/163490www/moinmoin port fix o ports/163467Ports using python 2.7 and waf intermittently hang o o ports/163441databases/couchdb multiple port installation issues. o ports/163314[maintainer update] www/ocsigen to version 2.0.2 o ports/163205graphics/gauche-gl won't build with gauche 0.9.2 f ports/163126security/sshguard changed from syslog.conf to daemon b o ports/163084net-mgmt/bsnmptools fails to build s ports/162996games/ioquake3-devel: update s2064-s2202 f ports/162743new port: benchmarks/worldbench, portable benchmark of o bin/162681 ports pkg_add(1): new installer does not add doc packages o ports/162676[NEW PORT] net-mgmt/ssgless: View ScreenOS configurati o ports/162674graphics/rawtherapee freezes after demosaic when tryin o ports/162588net/cvsup: cvsup and cvsupd get signal 10 under 9.0-RC o ports/162585group mismatch in mail/mailman o ports/162511[NEW PORT] net-im/imspector-devel devel version of ims o ports/162480New port: net-mgmt/cacti-with-plugins Web-driven graph f ports/162447net/isc-dhcp41-server: starting with rc-script fails o ports/162240net/nss-pam-ldapd should allow openldap24-sasl-client f ports/1622219.0-RC1 new problem building lang/spidermonkey f ports/162167New port: sysutils/torque2 s ports/162088inconsistencies in locally generated INDEX file o ports/162045print/ghostview 1.5_2 coredumps on certain files o ports/161867Revised Port: www/web-traceroute f ports/161694sysutils/dvd+rw-tools: growisofs fails to close disc o ports/161690New port: games/prboom-plus Port of ID Software's Doom o ports/161578devel/strace is not working o ports/161518[patch] update/add devel/scons version 2.1.0 o ports/161462net-mgmt/zabbix-agent: Zabbix_agentd opens a
Re: Feasibility of splitting out web components of lang/php5
Doug Barton ha scritto: What would make my life a whole lot simpler is if lang/php5 were the command line version, and the cgi and apache modules were separate ports. Is this feasible? Short answer: no. Long answer: nothing is impossible ;-) Extensions are compiled based on settings of the core php. If you split core php in different ports, you end up with possibly many different settings (e.g, standard CLI, debug CGI, threaded mod_php) and so it's impossible to compile extensions that work for all SAPIs. In an ideal world, the core php should compile only a shared library, and the various SAPIs should link it. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [patch] Problem building www/uwsgi on FreeBSD 9
Il giorno 08/gen/2012, alle ore 21:43, Maxim Khitrov ha scritto: Hi all, I'm not sure whether this is a FreeBSD or uwsgi problem, but the current port (uwsgi 1.0) isn't compiling on FreeBSD 9.0-RELEASE amd64 for the following reasons: 1. In uwsgiconfig.py:534 uwsgi checks for the existence of sys/capability.h. This header isn't present on my 7.x or 8.x systems, but it is there in FreeBSD 9. 2. If the check succeeds, UWSGI_CAP is defined for compilation. 3. In uwsgi.h:1169 the presence of UWSGI_CAP causes cap_value_t *cap; to be defined. 4. The FreeBSD version of sys/capability.h does not define cap_value_t (which seems to be a simple int typedef on Linux). The net effect of this is a long series of errors when compiling utils.c: FreeBSD9 capabilities are completely different from linux one. I will try to make a port, otherwise i will enable to check only for linux. -- Roberto De Ioris http://unbit.it JID: robe...@jabber.unbit.it ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
opendkim-2.4.2 missing files
Hi, Just in case this isn't a known issue.. cheers Paul. --- Upgrading 'opendkim-2.4.1' to 'opendkim-2.4.2' (mail/opendkim) --- Building '/usr/ports/mail/opendkim' === Cleaning for opendkim-2.4.2 === License BSD SENDMAIL accepted by the user === Found saved configuration for opendkim-2.4.1 = opendkim-2.4.2.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://heanet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://heanet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://sunet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://sunet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://iweb.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://iweb.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://switch.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://switch.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://surfnet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://surfnet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://kent.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://kent.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://freefr.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://freefr.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://voxel.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://voxel.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://jaist.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://jaist.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://osdn.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://osdn.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Not Found = Attempting to fetch http://nchc.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://nchc.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://ncu.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://ncu.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://transact.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://transact.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://softlayer.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://softlayer.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://internode.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://internode.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://ufpr.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://ufpr.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch http://waix.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz fetch: http://waix.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz: Moved Temporarily = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/opendkim-2.4.2.tar.gz fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/opendkim-2.4.2.tar.gz: File unavailable (e.g., file not found, no access) = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles/ and try again. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546PLEASE NOTE NEW MOBILE e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: USE_GCC and CC=clang
I'm trying to fix a port which absolutely will not build with clang, since clang does not support the gcc extension used by this port. I set USE_GCC=4.2+, which is the lowest version of GCC which will work, but it doesn't properly override CC=clang. wxs at ack spamdyke % env CC=clang make test-gcc | grep -E ^(CC|USE_GCC) USE_GCC=4.2+ CC=clang - CXX=c++ - CPP=cpp - CFLAGS=-O2 -pipe -fno-strict-aliasing wxs at ack spamdyke % This problem only arises if the base compiler is gcc 4.2.x and USE_GCC=4.2+. Otherwise CC will be set to the appropriate gcc compiler. Since Gerald (who maintains ports/Mk/bsd.gcc.mk) is trying to retire lang/gcc42 anyway, it is not a good idea to set USE_GCC=4.2+ in a port. I understand this is probably an acceptable behavior, since if the user sets CC=clang they are explicitly asking to build with clang. However, in the case of a port known to not work with clang, and more importantly not able to be fixed, I was hoping there was a knob I could set that would forcible override any compiler related environment variables which may be set. I didn't find one, so I came up with this quick (and poorly tested) patch to do so. The problem is due to a slight flaw in the implementation of the USE_GCC=4.2+ case, which will be obviated soon by the removal of this case. If in the meantime a change is made to bsd.gcc.mk, it should address this flaw directly -- by setting CC=gcc explicitly where needed, instead of relying upon the default setting of CC. Another knob is unnecessary. Note that changes to bsd.gcc.mk, good or bad, won't address the cases where a user sets CC on the command-line via make CC= ..., or adds it to MAKE_ARGS, or sets CC in the environment, and then calls make with -e or -E CC. So the right thing to do is to add something like: .if !empty(CC:M*clang*) IGNORE= : clang cannot be used to build this port .endif to the port Makefile, after the inclusion of bsd.port.options.mk or bsd.port.pre.mk (since a user may have set CC in Makefile.local, Makefile.inc, etc). Or, better yet, to patch the port so that it can be built with clang (which may have to be done anyway...). Regards, b. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [patch] Problem building www/uwsgi on FreeBSD 9
On Mon, Jan 9, 2012 at 10:13 AM, Roberto De Ioris robe...@unbit.it wrote: Il giorno 08/gen/2012, alle ore 21:43, Maxim Khitrov ha scritto: Hi all, I'm not sure whether this is a FreeBSD or uwsgi problem, but the current port (uwsgi 1.0) isn't compiling on FreeBSD 9.0-RELEASE amd64 for the following reasons: 1. In uwsgiconfig.py:534 uwsgi checks for the existence of sys/capability.h. This header isn't present on my 7.x or 8.x systems, but it is there in FreeBSD 9. 2. If the check succeeds, UWSGI_CAP is defined for compilation. 3. In uwsgi.h:1169 the presence of UWSGI_CAP causes cap_value_t *cap; to be defined. 4. The FreeBSD version of sys/capability.h does not define cap_value_t (which seems to be a simple int typedef on Linux). The net effect of this is a long series of errors when compiling utils.c: FreeBSD9 capabilities are completely different from linux one. I will try to make a port, otherwise i will enable to check only for linux. Yea, I spent a bit more time looking at it and the FreeBSD version of sys/capability.h seems to be related to libcapsicum rather than libcap. The POSIX version was removed ~9.5 years ago and resurrected as capacium 10 months ago for FreeBSD 9: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/capability.h Daniel, I suggest adding my patch to the port as a temporary solution. 9.0-RELEASE is likely to be announced any day now, so it would be good to have a working version of uwsgi in the ports tree. The patch can be removed once Roberto implements the final fix on his end. - Max uwsgi-capability.patch Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Perl symlinks question
Hi.
There is PR: http://bugs.freebsd.org/163687
It tries to fix port building when user built it's perl installation
with USE_PERL option (creating symlinks in /usr/bin) set to off (not the
default). Patch in PR just replaces static shebang with ${PERL} variable
from Mk/bsd.perl.mk. But it doesn't actually fix the build, because
consequent call of aclocal-1.11 will fail since it's shebang set to
'/usr/bin/perl' too.
The question is how to properly handle this PR:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
3. Close PR as invalid since the build fails because of user
intervention (changing the value of default option)
Thanks.
As for me, i believe second option is more preferable, but i don't know
if there something behind this.
PS. I think patch attached (for bsd.perl.mk) should be considered since
we no more have perl in base. And i'd also exclude perl-5.6.* from
CONFLICTS in lang/perl*, because it's something so ancient and doubtful
to face with.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
--- bsd.perl.mk.orig2011-08-15 10:50:00.0 +0400
+++ bsd.perl.mk 2012-01-09 22:43:00.0 +0400
@@ -11,10 +11,8 @@
# Please send all suggested changes to the maintainer instead of committing
# them to CVS yourself.
#
-# PERL5- Set to full path of perl5, either in the
system or
-#installed from a port.
-# PERL - Set to full path of perl5, either in the system or
-#installed from a port, but without the
version number.
+# PERL5- Set to full path of perl5
+# PERL - Set to full path of perl5, but without the version
number.
#Use this if you need to replace #! lines in
scripts.
# PERL_VERSION - Full version of perl5 (see below for current value).
# PERL_LEVEL - Perl version as an integer of the form MNNNPP, where
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
Adding perl and skv@
On 9 January 2012 18:49, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Hi.
There is PR: http://bugs.freebsd.org/163687
It tries to fix port building when user built it's perl installation with
USE_PERL option (creating symlinks in /usr/bin) set to off (not the
default). Patch in PR just replaces static shebang with ${PERL} variable
from Mk/bsd.perl.mk. But it doesn't actually fix the build, because
consequent call of aclocal-1.11 will fail since it's shebang set to
'/usr/bin/perl' too.
The question is how to properly handle this PR:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
3. Close PR as invalid since the build fails because of user
intervention (changing the value of default option)
Thanks.
As for me, i believe second option is more preferable, but i don't know if
there something behind this.
PS. I think patch attached (for bsd.perl.mk) should be considered since we
no more have perl in base. And i'd also exclude perl-5.6.* from CONFLICTS in
lang/perl*, because it's something so ancient and doubtful to face with.
I don't see any point in the symlink being optional either -- I vote for 2.
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [patch] Problem building www/uwsgi on FreeBSD 9
On 9.1.2012 19:35, Maxim Khitrov wrote: FreeBSD9 capabilities are completely different from linux one. I will try to make a port, otherwise i will enable to check only for linux. Yea, I spent a bit more time looking at it and the FreeBSD version of sys/capability.h seems to be related to libcapsicum rather than libcap. The POSIX version was removed ~9.5 years ago and resurrected as capacium 10 months ago for FreeBSD 9: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/capability.h yep, this is related to the Capsicum project of Robert Watson and some other people from Cambridge University. I don't know much about it though. Daniel, I suggest adding my patch to the port as a temporary solution. 9.0-RELEASE is likely to be announced any day now, so it would be good to have a working version of uwsgi in the ports tree. The patch can be removed once Roberto implements the final fix on his end. oki, I will look at it tonight. -- S pozdravom / Best regards Daniel Gerzo, FreeBSD committer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
2012/1/9 Chris Rees cr...@freebsd.org:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
/usr/bin is in LOCALBASE which may be read only.
--
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
Eitan Adler wrote on 09.01.2012 23:32:
2012/1/9 Chris Reescr...@freebsd.org:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
/usr/bin is in LOCALBASE which may be read only.
Ok, but if so most part of ports tree will not build on such systems,
because automake tools (aclocal in particular) calling /usr/bin/perl.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
On Mon, Jan 9, 2012 at 2:36 PM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
Eitan Adler wrote on 09.01.2012 23:32:
2012/1/9 Chris Reescr...@freebsd.org:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
/usr/bin is in LOCALBASE which may be read only.
Ok, but if so most part of ports tree will not build on such systems,
because automake tools (aclocal in particular) calling /usr/bin/perl.
The option should remain on by default due to the majority use case,
but elimination the option is a bad idea. Users should not have to
hack ports to use a readonly LOCALBASE.
--
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
On 1/9/2012 8:42 PM, Eitan Adler wrote:
On Mon, Jan 9, 2012 at 2:36 PM, Ruslan Mahmatkhanovcvs-...@yandex.ru wrote:
Eitan Adler wrote on 09.01.2012 23:32:
2012/1/9 Chris Reescr...@freebsd.org:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
/usr/bin is in LOCALBASE which may be read only.
Ok, but if so most part of ports tree will not build on such systems,
because automake tools (aclocal in particular) calling /usr/bin/perl.
The option should remain on by default due to the majority use case,
but elimination the option is a bad idea. Users should not have to
hack ports to use a readonly LOCALBASE.
Last time I installed perl with /usr/bin readonly (ezjail) it failed
silently to create the symlink so there is really no reason to switch
this option off.
That's why, I would also go for option 2/
If you have a readonly /usr/bin, it is the job of your administrator
(that'd be you!) to create the symlink.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: opendkim-2.4.2 missing files
On 2012-01-09 18:23, Paul Macdonald wrote:
Hi,
Just in case this isn't a known issue..
cheers
Paul.
--- Upgrading 'opendkim-2.4.1' to 'opendkim-2.4.2' (mail/opendkim)
--- Building '/usr/ports/mail/opendkim'
[...]
= Couldn't fetch it - please try to retrieve this
= port manually into /usr/ports/distfiles/ and try again.
Download link fixed (and comitted), souce file was moved to Previous Releases
--- opendkim/Makefile 8 Jan 2012 01:23:47 - 1.9
+++ opendkim/Makefile 9 Jan 2012 19:58:30 -
@@ -9,7 +9,7 @@
PORTVERSION= 2.4.2
CATEGORIES=mail security
MASTER_SITES= SF
-MASTER_SITE_SUBDIR=${PORTNAME}
+MASTER_SITE_SUBDIR=${PORTNAME}/Previous%20Releases/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: opendkim-2.4.2 missing files
On Mon, Jan 09, 2012 at 09:04:25PM +0100, Olli Hauer wrote: On 2012-01-09 18:23, Paul Macdonald wrote: Hi, Just in case this isn't a known issue.. cheers Paul. --- Upgrading 'opendkim-2.4.1' to 'opendkim-2.4.2' (mail/opendkim) --- Building '/usr/ports/mail/opendkim' [...] = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles/ and try again. Download link fixed (and comitted), souce file was moved to Previous Releases Is it hard to just update this port to the latest version instead? (CC'ed to the maintainer) -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD9 + PHP
so maybe there is package to make existing php5 package that would work w/ apache and not just fastcgi On Mon, Jan 9, 2012 at 3:06 PM, Chuck Swiger cswi...@mac.com wrote: On Jan 9, 2012, at 12:02 PM, alexus wrote: there is no way to make it like that? so it has to be build via ports? The PHP maintainer decides the default options, which is what the precompiled package you got used. While many people want PHP in the form of an Apache module, other folks use it via fastcgi and so forth... Regards, -- -Chuck -- http://alexus.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: opendkim-2.4.2 missing files
On 1/9/12 3:17 PM, Andrey Chernov wrote: Is it hard to just update this port to the latest version instead? (CC'ed to the maintainer) I have seen several of these before. problem is, tuesday, you update the port. works wednesday, thursday and friday. by monday, they moved it. so, you HOPEFULLY, can ALWAYS pull 'previous_version/ver/dist/patch.tgz' or, you are just chasing your tail. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
archivers/zip in 9.x:
I think I saw something in the list that FreeBSD 9.x has zip already
built in? so, ports that need 'zip' won't need zip?
for maintainers, they should use something like:
USE_ZIP=yes
to:
if ${OSVERSION} = 90
USE_ZIP=yes
.endif
and/or BUILD_DEPENDS+=zip:${PORTSDIR}/archivers/zip
(at what OSVERSION was zip included in the base?)
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
__
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
__
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
archivers/zip in 9.x:
I think I saw something in the list that FreeBSD 9.x has zip already
built in? so, ports that need 'zip' won't need zip?
for maintainers, they should use something like:
USE_ZIP=yes
to:
if ${OSVERSION} = 90
USE_ZIP=yes
.endif
and/or BUILD_DEPENDS+=zip:${PORTSDIR}/archivers/zip
(at what OSVERSION was zip included in the base?)
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
__
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
__
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
Michael Scheidell wrote on 10.01.2012 00:30:
I think I saw something in the list that FreeBSD 9.x has zip already
built in? so, ports that need 'zip' won't need zip?
for maintainers, they should use something like:
USE_ZIP= yes
to:
if ${OSVERSION} = 90
USE_ZIP= yes
.endif
and/or BUILD_DEPENDS+= zip:${PORTSDIR}/archivers/zip
(at what OSVERSION was zip included in the base?)
unzip, not zip. I believe it should be handled in bsd.port.mk like it
done for USE_XZ. Something like:
.if defined(USE_ZIP) ${OSVERSION} 90
EXTRACT_DEPENDS+= ${LOCALBASE}/bin/unzip:${PORTSDIR}/archivers/unzip
.endif
Correct OSVERSION should be used instead of 90. There is also should
be some logic for UNZIP_CMD.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: opendkim-2.4.2 missing files
On 2012-01-09 21:17, Andrey Chernov wrote:
On Mon, Jan 09, 2012 at 09:04:25PM +0100, Olli Hauer wrote:
On 2012-01-09 18:23, Paul Macdonald wrote:
Hi,
Just in case this isn't a known issue..
cheers
Paul.
--- Upgrading 'opendkim-2.4.1' to 'opendkim-2.4.2' (mail/opendkim)
--- Building '/usr/ports/mail/opendkim'
[...]
= Couldn't fetch it - please try to retrieve this
= port manually into /usr/ports/distfiles/ and try again.
Download link fixed (and comitted), souce file was moved to Previous
Releases
Is it hard to just update this port to the latest version instead?
(CC'ed to the maintainer)
I think the new 2.4.3 version should be reviewed be the maintainer, because
there is also a new configure option for ldns.
Since I agree wit Michael, maybe we should change MASTER_SITE_SUBDIR to the
following expression.
- MASTER_SITE_SUBDIR= ${PORTNAME}/Previous%20Releases
+ MASTER_SITE_SUBDIR= ${PORTNAME} \
+ ${PORTNAME}/Previous%20Releases
In case the source is moved to Previous Releases is not broken.
= Attempting to fetch
http://heanet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz
fetch: http://heanet.dl.sourceforge.net/project/opendkim/opendkim-2.4.2.tar.gz:
Moved Temporarily
= Attempting to fetch
http://heanet.dl.sourceforge.net/project/opendkim/Previous%20Releases/opendkim-2.4.2.tar.gz
opendkim-2.4.2.tar.gz 100% of 1342 kB 1052 kBps
--
Cheers,
olli
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
Ruslan Mahmatkhanov wrote on 10.01.2012 01:06:
Michael Scheidell wrote on 10.01.2012 00:30:
I think I saw something in the list that FreeBSD 9.x has zip already
built in? so, ports that need 'zip' won't need zip?
for maintainers, they should use something like:
USE_ZIP= yes
to:
if ${OSVERSION} = 90
USE_ZIP= yes
.endif
and/or BUILD_DEPENDS+= zip:${PORTSDIR}/archivers/zip
(at what OSVERSION was zip included in the base?)
unzip, not zip. I believe it should be handled in bsd.port.mk like it
done for USE_XZ. Something like:
.if defined(USE_ZIP) ${OSVERSION} 90
EXTRACT_DEPENDS+= ${LOCALBASE}/bin/unzip:${PORTSDIR}/archivers/unzip
.endif
Correct OSVERSION should be used instead of 90. There is also should
be some logic for UNZIP_CMD.
.if exists(/usr/bin/unzip)
UNZIP_CMD?=/usr/bin/unzip
.else
UNZIP_CMD?=${LOCALBASE}/bin/unzip
.endif
in bsd.commands.mk
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 1/9/12 4:06 PM, Ruslan Mahmatkhanov wrote:
(at what OSVERSION was zip included in the base?)
unzip, not zip. I believe it should be handled in bsd.port.mk like it
done for USE_XZ. Something like:
.if defined(USE_ZIP) ${OSVERSION} 90
EXTRACT_DEPENDS+=
${LOCALBASE}/bin/unzip:${PORTSDIR}/archivers/unzip
.endif
Correct OSVERSION should be used instead of 90. There is also
should be some logic for UNZIP_CMD.
any idea what OSVERSION that would be? 900045 ?
EXTRACT_DEPENDS.. yes, forgot.
because, TODAY:
make -V OSVERSION
900044
grep ZIP /usr/ports/Mk/bsd.*
/usr/ports/Mk/bsd.commands.mk:UNZIP_CMD?=${LOCALBASE}/bin/unzip
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
__
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com/
__
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 1/9/12 4:10 PM, Ruslan Mahmatkhanov wrote:
.if exists(/usr/bin/unzip)
UNZIP_CMD?=/usr/bin/unzip
.else
UNZIP_CMD?=${LOCALBASE}/bin/unzip
.endif
in bsd.commands.mk
not in 900044
grep /usr/bin/zip /usr/ports/Mk/*
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/9/12 4:14 PM, Michael Scheidell wrote:
On 1/9/12 4:10 PM, Ruslan Mahmatkhanov wrote:
.if exists(/usr/bin/unzip)
UNZIP_CMD?=/usr/bin/unzip
.else
UNZIP_CMD?=${LOCALBASE}/bin/unzip
.endif
in bsd.commands.mk
not in 900044
grep /usr/bin/zip /usr/ports/Mk/*
This list of version values is very helpful in these cases:
http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html
Unfortunately, the version was not bumped when unzip was added to base,
but you'll probably be able to narrow down where to look after
consulting that page.
Cheers,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8LWtIACgkQ0sRouByUApDoNACgkt3u0f1IBoVcgs4D6dqIZL2W
HD8An0loEdGwnpIUg5gWuiCIjsogkMrd
=7Q35
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 1/9/12 4:23 PM, Greg Larkin wrote: This list of version values is very helpful in these cases: http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html Unfortunately, the version was not bumped when unzip was added to base, but you'll probably be able to narrow down where to look after consulting that page. thanks, yes, I did look and didn't see the delta version number. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On Tue, Jan 10, 2012 at 01:06:04AM +0400, Ruslan Mahmatkhanov wrote:
Michael Scheidell wrote on 10.01.2012 00:30:
I think I saw something in the list that FreeBSD 9.x has zip already
built in? so, ports that need 'zip' won't need zip?
for maintainers, they should use something like:
USE_ZIP= yes
to:
if ${OSVERSION} = 90
USE_ZIP= yes
.endif
and/or BUILD_DEPENDS+= zip:${PORTSDIR}/archivers/zip
(at what OSVERSION was zip included in the base?)
unzip, not zip. I believe it should be handled in bsd.port.mk like it
done for USE_XZ. Something like:
.if defined(USE_ZIP) ${OSVERSION} 90
EXTRACT_DEPENDS+= ${LOCALBASE}/bin/unzip:${PORTSDIR}/archivers/unzip
.endif
Correct OSVERSION should be used instead of 90. There is also should
be some logic for UNZIP_CMD.
A few things need to be done before it will be possible to use the
native unzip in CURRENT:
1) pr153429
2) mfv libarchive's seekable zip reader
3) patch to bsd.port.mk which implements USE_ZIP = yes|native|infozip
4) few tinderbox runs
--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 2012-01-09 22:23, Greg Larkin wrote:
On 1/9/12 4:14 PM, Michael Scheidell wrote:
On 1/9/12 4:10 PM, Ruslan Mahmatkhanov wrote:
.if exists(/usr/bin/unzip)
UNZIP_CMD?=/usr/bin/unzip
.else
UNZIP_CMD?=${LOCALBASE}/bin/unzip
.endif
in bsd.commands.mk
not in 900044
grep /usr/bin/zip /usr/ports/Mk/*
This list of version values is very helpful in these cases:
http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html
Unfortunately, the version was not bumped when unzip was added to base,
but you'll probably be able to narrow down where to look after
consulting that page.
Have at the moment no 7.x machine handy but zip files can be handled by tar, at
last here on a 8.2 machine and I have no unzip installed.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 1/9/12 4:46 PM, olli hauer wrote: Have at the moment no 7.x machine handy but zip files can be handled by tar, at last here on a 8.2 machine and I have no unzip installed. hey, don't confuse me. -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: php5-5.3.8
Hello I'm trying to migrate from REDHAT EL world to FREEBSD. We have a policy of installing binary packages and stay away from compiling source code. I have FreeBSD-9.0RC3 and I did pkg_add -r apache22 pkg_add -r php5, so now I have both packages installed but I can't get them to work together... am I doing something wrong? or was it not meant to work together? or there is something else needs to be done that I'm missing? if possible I'd like to stay away from (/usr/ports), as we want to use packages only thanks.___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 9 Jan 2012 21:16, Michael Scheidell scheid...@freebsd.org wrote:
On 1/9/12 4:10 PM, Ruslan Mahmatkhanov wrote:
.if exists(/usr/bin/unzip)
UNZIP_CMD?=/usr/bin/unzip
.else
UNZIP_CMD?=${LOCALBASE}/bin/unzip
.endif
in bsd.commands.mk
not in 900044
grep /usr/bin/zip /usr/ports/Mk/*
Just use the later value (900045?). Once a release is cut, old CURRENT on
that branch is no longer supported anyway.
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: php5-5.3.8
On Mon, 09 Jan 2012 15:52:19 -0600, ale...@alexus.org wrote: Hello I'm trying to migrate from REDHAT EL world to FREEBSD. We have a policy of installing binary packages and stay away from compiling source code. I have FreeBSD-9.0RC3 and I did pkg_add -r apache22 pkg_add -r php5, so now I have both packages installed but I can't get them to work together... am I doing something wrong? or was it not meant to work together? or there is something else needs to be done that I'm missing? if possible I'd like to stay away from (/usr/ports), as we want to use packages only The Apache module is missing and I don't know if there's a package for that or if you really do have to use ports. I've never tried using just packages for Apache+PHP. Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 2012-01-09 23:18, Michael Scheidell wrote: On 1/9/12 4:46 PM, olli hauer wrote: Have at the moment no 7.x machine handy but zip files can be handled by tar, at last here on a 8.2 machine and I have no unzip installed. hey, don't confuse me. Don't worry, I believe you will do the right thing ;) ( Chris just confirmed that tar can extract zip files also on 7.4 and he use this in games/ioquake3) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 1/9/12 5:36 PM, Olli Hauer wrote: Don't worry, I believe you will do the right thing ;) ( Chris just confirmed that tar can extract zip files also on 7.4 and he use this in games/ioquake3) so, that means we can use tar in 8.x and 9.x. we didn't need unzip... :0-) so, I am a ports committer, how about I hack bsd.port.*.mk files :-) -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
--On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: php5-5.3.8
On 1/9/12 4:52 PM, alexus wrote:
Hello
I'm trying to migrate from REDHAT EL world to FREEBSD. We have a policy of
installing binary packages and stay away from compiling source code.
I have FreeBSD-9.0RC3 and I did pkg_add -r apache22 pkg_add -r php5, so now I
have both packages installed but I can't get them to work together...
you can compile your own, and use that from now on.
instead of 'make install' do a 'make package' from the /usr/ports tree.
What you need to understand about the 'pkg_add -r' is that this is a
SNAPSHOT IN TIME, and uses the BUILD IN DEFAULT OPTIONS (sorry, about
the shouting), but this is important.
9.x is NOT released yet, so, to say you want the pre-build binaries is
also a moving target.
on a second box, if you don't want to touch your production box, make
the individual packages with your options, make packages, put them
somethere, and then use pkg_add -r {your url} to add the package.
you could even do something like:
pkg_add -r {your url} {package} || pkg_add -r {your package} that
would look, first for YOUR package, then the pre-build one that is
static and you should not use anyway..
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
*| *SECNAP Network Security Corporation
* Best Mobile Solutions Product of 2011
* Best Intrusion Prevention Product
* Hot Company Finalist 2011
* Best Email Security Product
* Certified SNORT Integrator
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: php5-5.3.8
On 2012-01-09 23:31, Mark Felder wrote: On Mon, 09 Jan 2012 15:52:19 -0600, ale...@alexus.org wrote: Hello I'm trying to migrate from REDHAT EL world to FREEBSD. We have a policy of installing binary packages and stay away from compiling source code. I have FreeBSD-9.0RC3 and I did pkg_add -r apache22 pkg_add -r php5, so now I have both packages installed but I can't get them to work together... am I doing something wrong? or was it not meant to work together? or there is something else needs to be done that I'm missing? if possible I'd like to stay away from (/usr/ports), as we want to use packages only The Apache module is missing and I don't know if there's a package for that or if you really do have to use ports. I've never tried using just packages for Apache+PHP. Yes, the default option for lang/php5 is to build *no* apache module, so I suspect you have to build php from source with option APACHE set to on. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 09/01/2012 22:28, Paul Schmehl wrote: --On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? rpms are usually digitally signed. Short of grabbing an appropriate flavour of linux and running yum or whatever on it I wouldn't know how to go about checking that signature though. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Jan 9, 2012, at 2:28 PM, Paul Schmehl wrote: My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? rpm -Va (or rpm --verify --all) ought to consult an MD5 checksum to identify changes for all installed packages... Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On 2012-01-09 23:39, Michael Scheidell wrote: On 1/9/12 5:36 PM, Olli Hauer wrote: Don't worry, I believe you will do the right thing ;) ( Chris just confirmed that tar can extract zip files also on 7.4 and he use this in games/ioquake3) so, that means we can use tar in 8.x and 9.x. we didn't need unzip... :0-) so, I am a ports committer, how about I hack bsd.port.*.mk files :-) depends ... grep MAINTAINER ports/Mk/bsd.port* Maybe an exp-run or a second review from portmgr@ is needed? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
Ruslan Mahmatkhanov cvs-...@yandex.ru writes:
There is PR: http://bugs.freebsd.org/163687
It tries to fix port building when user built it's perl installation
with USE_PERL option (creating symlinks in /usr/bin) set to off (not
the default). Patch in PR just replaces static shebang with ${PERL}
variable from Mk/bsd.perl.mk. But it doesn't actually fix the build,
because consequent call of aclocal-1.11 will fail since it's shebang
set to '/usr/bin/perl' too.
[...]
Can you shed more light on the aclocal issue? Does the submitter know?
nss_ldap installs fine after applying ports/163687.
$ ls -1d /usr/local/share/aclocal*
/usr/local/share/aclocal/
/usr/local/share/aclocal-1.11/
/usr/local/share/aclocal-1.4/
$ fgrep -r /usr/bin/perl /usr/local/share/aclocal*
Exit 1
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: php5-5.3.8
On 09/01/2012 21:52, alexus wrote: I'm trying to migrate from REDHAT EL world to FREEBSD. We have a policy of installing binary packages and stay away from compiling source code. I have FreeBSD-9.0RC3 and I did pkg_add -r apache22 pkg_add -r php5, so now I have both packages installed but I can't get them to work together... You might want to review that policy if you're going to move to FreeBSD. Much of the unique benefit of the ports system is obtained through using it to compile software (which you can tune to your specific use case much better) rather than by installing generic binary packages. The apache22 port is a particularly good example. If you go to compile that from ports, you'll find you can tailor pretty much every apache module that gets included in your system, plus you have an unprecedented degree of control over what gets built into the apache portable runtime layer as well. Meaning you can really slim down and get more apache processes into your available memory, hence greater throughput. On the other hand, it is a bit daunting to wade through all those options if you aren't very familiar with them and don't know what is really needed, and what can be cast aside. Yes, compilation takes a bit longer than download+install, but not a huge amount greater in most cases. (Some ports are monsters and take ages to build, but they are exceptional.) Ports does make it quite simple to build your own binary packages with all your required customizations, which you can then use to manage your live systems. The best of both worlds really. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: ports vs packages
On Jan 9, 2012, at 2:00 PM, alexus wrote: One of the things I'm seeing is that unfortunately packages are somewhat limited vs ports... Packages come precompiled with default options. For people who want non-default options, you would need to build your own package from ports rather than using the precompiled one. For example: I'm trying to get Apache httpd + PHP to work, after pkg_add -r php5, php5 doesn't have libphp5.so that links Apache and PHP together... so unless I'm doing something entirely wrong I basically must use ports and nothing else to get the functionality i need... You can use ports and packages together just fine. In particular, you ought to be able to use the Apache-2.x package with a php5 port that you build to enable mod_php. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/10/12 08:28, Paul Schmehl wrote: --On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? I don't know. I believe they have a gpg key they use, at least with their repo system. How that specifically works I don't know. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
Op ma 09 jan 2012 22:49:33 schreef Ruslan Mahmatkhanov:
Hi.
There is PR: http://bugs.freebsd.org/163687
It tries to fix port building when user built it's perl installation
with USE_PERL option (creating symlinks in /usr/bin) set to off (not the
default). Patch in PR just replaces static shebang with ${PERL} variable
from Mk/bsd.perl.mk. But it doesn't actually fix the build, because
consequent call of aclocal-1.11 will fail since it's shebang set to
'/usr/bin/perl' too.
The question is how to properly handle this PR:
1. Fix devel/automake too (by replacing /usr/bin/perl with ${PERL})
2. Create symlinks unconditionally in perl port and drop USE_PERL option
3. Close PR as invalid since the build fails because of user
intervention (changing the value of default option)
4. Teach upstream (and maybe maintainers) to use /usr/bin/env as they should
do:
http://perldoc.perl.org/perlintro.html#Running-Perl-programs
(this goes for multimedia/ffmpeg or rather texipod.pl included in that build,
too)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD9 + PHP
On 01/09/2012 12:08, alexus wrote: so maybe there is package to make existing php5 package that would work w/ apache and not just fastcgi There is not a package with that option enabled. You will need to build /usr/ports/lang/php5 and run 'make config' to enable it. Hope this helps, Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: archivers/zip in 9.x:
On Mon, Jan 09, 2012 at 05:39:03PM -0500, Michael Scheidell wrote: so, I am a ports committer, how about I hack bsd.port.*.mk files :-) Commits to bsd.port.mk need to be approved by portmgr, preferably after regression-testing on the cluster. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD9 + PHP
ok, thanks On Mon, Jan 9, 2012 at 7:02 PM, Doug Barton do...@freebsd.org wrote: On 01/09/2012 12:08, alexus wrote: so maybe there is package to make existing php5 package that would work w/ apache and not just fastcgi There is not a package with that option enabled. You will need to build /usr/ports/lang/php5 and run 'make config' to enable it. Hope this helps, Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ -- http://alexus.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: define issue - linux-f10-nss_ldap: my first port - be gentle :)
I'm having some trouble using knobs and defined in the Makefile. It keeps complaining about the unexpected. I've tried .if defined(WITH_PAM) and .ifdefined(WITH_PAM) and it complains about an unexpected ( in the first, and an unexpected word in the second. How do I conditionally handle the knobs? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: USE_GCC and CC=clang
On Mon, Jan 09, 2012 at 06:22:58PM +, b. f. wrote: I'm trying to fix a port which absolutely will not build with clang, since clang does not support the gcc extension used by this port. I set USE_GCC=4.2+, which is the lowest version of GCC which will work, but it doesn't properly override CC=clang. wxs at ack spamdyke % env CC=clang make test-gcc | grep -E ^(CC|USE_GCC) USE_GCC=4.2+ CC=clang - CXX=c++ - CPP=cpp - CFLAGS=-O2 -pipe -fno-strict-aliasing wxs at ack spamdyke % This problem only arises if the base compiler is gcc 4.2.x and USE_GCC=4.2+. Otherwise CC will be set to the appropriate gcc compiler. Since Gerald (who maintains ports/Mk/bsd.gcc.mk) is trying to retire lang/gcc42 anyway, it is not a good idea to set USE_GCC=4.2+ in a port. Thanks for the pointer. I understand this is probably an acceptable behavior, since if the user sets CC=clang they are explicitly asking to build with clang. However, in the case of a port known to not work with clang, and more importantly not able to be fixed, I was hoping there was a knob I could set that would forcible override any compiler related environment variables which may be set. I didn't find one, so I came up with this quick (and poorly tested) patch to do so. The problem is due to a slight flaw in the implementation of the USE_GCC=4.2+ case, which will be obviated soon by the removal of this case. If in the meantime a change is made to bsd.gcc.mk, it should address this flaw directly -- by setting CC=gcc explicitly where needed, instead of relying upon the default setting of CC. Another knob is unnecessary. Note that changes to bsd.gcc.mk, good or bad, won't address the cases where a user sets CC on the command-line via make CC= ..., or adds it to MAKE_ARGS, or sets CC in the environment, and then calls make with -e or -E CC. So the right thing to do is to add something like: .if !empty(CC:M*clang*) IGNORE= : clang cannot be used to build this port .endif to the port Makefile, after the inclusion of bsd.port.options.mk or bsd.port.pre.mk (since a user may have set CC in Makefile.local, Makefile.inc, etc). Or, better yet, to patch the port so that it can be built with clang (which may have to be done anyway...). I was hoping to not have to set IGNORE if using clang. I'm also not really interested in patching the port, since it's more about structural changes than a simple fixes. I guess I'll set the IGNORE line if using clang for now. No point in wasting cycles on a port which won't compile for a long time, if ever. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Perl symlinks question
Jan Beich wrote on 10.01.2012 03:06:
Ruslan Mahmatkhanovcvs-...@yandex.ru writes:
There is PR: http://bugs.freebsd.org/163687
It tries to fix port building when user built it's perl installation
with USE_PERL option (creating symlinks in /usr/bin) set to off (not
the default). Patch in PR just replaces static shebang with ${PERL}
variable from Mk/bsd.perl.mk. But it doesn't actually fix the build,
because consequent call of aclocal-1.11 will fail since it's shebang
set to '/usr/bin/perl' too.
[...]
Can you shed more light on the aclocal issue? Does the submitter know?
nss_ldap installs fine after applying ports/163687.
$ ls -1d /usr/local/share/aclocal*
/usr/local/share/aclocal/
/usr/local/share/aclocal-1.11/
/usr/local/share/aclocal-1.4/
$ fgrep -r /usr/bin/perl /usr/local/share/aclocal*
Exit 1
Sure.
=== Configuring for nss_ldap-1.265_7
env: /usr/local/bin/aclocal-1.11: No such file or directory
*** Error code 127
[rm@smeshariki3 ~/learn] head -3 `which aclocal-1.11`
#!/usr/bin/perl -w
# -*- perl -*-
# Generated from aclocal.in; do not edit by hand.
Submitter doesn't seems know about (or didn't faced this).
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Porter's Handbook: PREFIX and DESTDIR
The updated PREFIX and DESTDIR section has been committed. Thanks for the feedback and suggestions! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
compiling py-* ports for python32
I'd like to install a couple of the python module ports as part of my python32 install (also from ports). Is there an incantation I can use with portinstall or the ports Makefile that will allow me to tell typical py-* modules in my python 3.2 libraries instead of with python 2.7, or should I be looking at cloning py-* ports into nearly-identical py32-* ports and submitting them? Thanks for any pointers! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: compiling py-* ports for python32
Try add this line in /etc/make.conf PYTHON_DEFAULT_VERSION=python3.2 wen 2012/1/10 Matthew Pounsett m...@conundrum.com I'd like to install a couple of the python module ports as part of my python32 install (also from ports). Is there an incantation I can use with portinstall or the ports Makefile that will allow me to tell typical py-* modules in my python 3.2 libraries instead of with python 2.7, or should I be looking at cloning py-* ports into nearly-identical py32-* ports and submitting them? Thanks for any pointers! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: compiling py-* ports for python32
On 2012/01/10, at 01:16, wen heping wrote: Try add this line in /etc/make.conf PYTHON_DEFAULT_VERSION=python3.2 Perfect! Thanks very much! One of the dependencies turns out to have a syntax dependency on python2.x, but I can work with that. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
