FreeBSD Port: spamcup-1.09_2
Hello, It looks like spamcup is missing a dependency on www/p5-HTML-Form. Perhaps it was previously a dependency of p5-libwww and the recent changes made it no longer a dependency. Thanks! -- Douglas William Thrift douglas...@gmail.com http://douglasthrift.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: RFC: change to bsd.perl.mk
On 17 July 2011 01:47, Doug Barton do...@freebsd.org wrote: On 07/16/2011 17:35, Mark Linimon wrote: On Sat, Jul 16, 2011 at 10:51:04PM +0100, Chris Rees wrote: If it's unconditionally included, how does that exempt it from exp-runs? Surely it's equally risky to commit to it as bsd.port.mk, or have I missed something? In a perfect world we'd have -exp runs for everything, I suppose. OTOH here in the real world there's plenty of lower-risk changes that can be done without. If in doubt, we can always do one. Take a look a the various commits in ports/Mk for examples of what's been done in the past. A) If the file is unconditionally included the idea of administrative separation is false security. There is no reason that the appropriate perl folks can't have permission to twiddle that stuff in bpm. B) Focusing on this part of the problem detracts from the more important point that the thing should be conditionally included, and that whatever needs to be fixed to make that happen should be fixed. Doug, Am I right in thinking from your comments in the past that you would be willing to form a team to achieve this goal? I think you're right, and it should be done -- count me in. 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: RFC: change to bsd.perl.mk
On 07/17/2011 03:07, Chris Rees wrote: On 17 July 2011 01:47, Doug Barton do...@freebsd.org wrote: On 07/16/2011 17:35, Mark Linimon wrote: On Sat, Jul 16, 2011 at 10:51:04PM +0100, Chris Rees wrote: If it's unconditionally included, how does that exempt it from exp-runs? Surely it's equally risky to commit to it as bsd.port.mk, or have I missed something? In a perfect world we'd have -exp runs for everything, I suppose. OTOH here in the real world there's plenty of lower-risk changes that can be done without. If in doubt, we can always do one. Take a look a the various commits in ports/Mk for examples of what's been done in the past. A) If the file is unconditionally included the idea of administrative separation is false security. There is no reason that the appropriate perl folks can't have permission to twiddle that stuff in bpm. B) Focusing on this part of the problem detracts from the more important point that the thing should be conditionally included, and that whatever needs to be fixed to make that happen should be fixed. Doug, Am I right in thinking from your comments in the past that you would be willing to form a team to achieve this goal? Yes. I think you're right, and it should be done -- count me in. Chris -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go 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: ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
On Sat July 16 2011 18:21:12 Chris Rees wrote:
Bear in mind they should work fine if the port doesn't hardcode absolute
paths.
Yes, they actually do! Please do not remove them, because they are not as
buggy as it is claimed here. I often use the -p option for testing of my
tinderbox -exp packages and it works fine.
A package is basically the same as an installed port - just with some
additional pkg meta data files all packed into a compressed tarball. If a
package contains hardcoded paths then the port is buggy not the package or
pkg_add. It is a general rule that ports should respect ${PREFIX}. If they do
not those ports need to be fixed.
I find it weird to think the -p / -P options should be removed from pkg_add.
Do not castrate the tool if some ports are buggy!
Thanks!
--
Regards
signature.asc
Description: This is a digitally signed message part.
mail/py-spambayes - a patch to make it work with Python 2.7
Hi,
Time flies fast. WE now have Python 2.7 and 3.2 in our system, not Python 2.6.
The following patch makes mail/py-spambayes use Python 2.7.
root@kg-v2# diff -u Makefile.org Makefile
--- Makefile.org2009-08-22 02:27:53.0 +0200
+++ Makefile2011-07-17 14:22:51.0 +0200
@@ -18,7 +18,7 @@
# bypass infrastructure bug
OPTIONSFILE= ${PORT_DBDIR}/py-${PORTNAME}/options
-OPTIONS= PYTHON26Build with Python 2.6 (with unofficial patch)
off
+OPTIONS= PYTHON27Build with Python 2.7 (with unofficial patch)
off
USE_PYDISTUTILS= yes
USE_RC_SUBR= pyspamd
@@ -81,8 +81,8 @@
.include bsd.port.options.mk
-.if defined(WITH_PYTHON26)
-USE_PYTHON=2.6
+.if defined(WITH_PYTHON27)
+USE_PYTHON=2.7
RUN_DEPENDS+= ${PYTHON_SITELIBDIR}/_bsddb.so:${PORTSDIR}/databases/py-bsddb
EXTRA_PATCHES+=${FILESDIR}/extra-patch-python26
.else
AFAICT, spambayes works fine with this patch.
Not sure if the patch is good enough, so I haven't sent a PR yet.
--
Regards,
Torfinn Ingolfsen
___
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: spamcup-1.09_2
Doug, Good catch, I'll take care of this shortly. -r On (07/17/11 01:11), Douglas Thrift wrote: Hello, It looks like spamcup is missing a dependency on www/p5-HTML-Form. Perhaps it was previously a dependency of p5-libwww and the recent changes made it no longer a dependency. Thanks! -- Douglas William Thrift douglas...@gmail.com http://douglasthrift.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 -- Ryan Steinmetz PGP: EF36 D45A 5CA9 28B1 A550 18CD A43C D111 7AD7 FAF2 ___ 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
comms/umcs7840 doesn't compile under FreeBSD 8.2-stable
Hello, I just upgraded my machine to FreeBSD 8.2-stable (it was running 8.1-stable before): tingo@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 and now umcs7840-kmod doesn't compile: root@kg-v2# cd /usr/ports/comms/umcs7840 root@kg-v2# make clean === Cleaning for umcs7840-kmod-1.0.20101210.57 root@kg-v2# make === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Extracting for umcs7840-kmod-1.0.20101210.57 = SHA256 Checksum OK for umcs7840-1.0.20101210.57.tar.bz2. === Patching for umcs7840-kmod-1.0.20101210.57 === Configuring for umcs7840-kmod-1.0.20101210.57 === Building for umcs7840-kmod-1.0.20101210.57 === src (all) Warning: Object directory not changed from original /usr/ports/comms/umcs7840/work/umcs7840-1.0.20101210.57/src @ - /usr/src/sys machine - /usr/src/sys/amd64/include : opt_bus.h : opt_usb.h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/usb/usb_if.m -h awk -f @/tools/usbdevs2h.awk @/dev/usb/usbdevs -h cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c umcs7840.c umcs7840.c: In function 'umcs7840_detach': umcs7840.c:421: error: too many arguments to function 'ucom_detach' *** Error code 1 Stop in /usr/ports/comms/umcs7840/work/umcs7840-1.0.20101210.57/src. *** Error code 1 Stop in /usr/ports/comms/umcs7840/work/umcs7840-1.0.20101210.57. *** Error code 1 Stop in /usr/ports/comms/umcs7840. HTH -- Regards, Torfinn Ingolfsen ___ 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: ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
current - ports On 07/16/2011 09:02 PM, Adrian Chadd wrote: Unless say, you're doing package installation outside of a chroot/jail, to populate something inside a chroot/jail before you start said chroot/jail. I can see -P and -p working for those many ports which just put programs in place. But there are some ports that include installation programs as part of the software. And some ports (like octave) which have a program which sometimes acts as an installation script, and sometimes acts as a user program. And sometimes those installation programs install for the port, and sometimes they install for a subport. If we are to continue using the -P and -p options, I suggest someone does the following: 1. Spell out very clearly its purpose - is it to populate a jail, for example? 2. Set up a computer that tests each package to see if it is -P compliant and -p compliant. By the way, each should be tested separately. For example, suppose latex-pgf is installed with the -p option. Then does it expect mktexlsr to be in the directory it is installing into, or the regular directory? mktexlsr is installed by a dependency, so the package needs to know where to find it. It would seem to me that you need a PKG_LOCALBASE variable as well as a PKG_PREFIX variable, so that the port knows where to find these installation programs. 3. Add a flag to ports that allow the port maintainer to mark the port -p non-compliant and -P non-compliant. The other possibility is to add to the man page of pkg_add saying that there is a good chance the -p and -P options don't work properly. Some people have clearly indicated that they like and use these options, so let's keep them happy too, and not delete it altogether. Stephen ___ 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: ports/158179: some packages do not fully honor -P dir option in pkg_add(1)
On 17 July 2011 11:55, Marco Bröder marco.broe...@gmx.eu wrote:
On Sat July 16 2011 18:21:12 Chris Rees wrote:
Bear in mind they should work fine if the port doesn't hardcode absolute
paths.
Yes, they actually do! Please do not remove them, because they are not as
buggy as it is claimed here. I often use the -p option for testing of my
tinderbox -exp packages and it works fine.
A package is basically the same as an installed port - just with some
additional pkg meta data files all packed into a compressed tarball. If a
package contains hardcoded paths then the port is buggy not the package or
pkg_add. It is a general rule that ports should respect ${PREFIX}. If they do
not those ports need to be fixed.
I find it weird to think the -p / -P options should be removed from pkg_add.
Do not castrate the tool if some ports are buggy!
By no means is it a bug if paths are hardcoded into compiled binaries
-- it's common practice and unfortunately this will not change.
Another consequence of this is that most programs can't be relocated
to a different part of the filesystem.
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: audio/musicpd and libsndfile dependency
On 16/07/2011 15:13, Chris Rees wrote: On 16 Jul 2011 13:03, David Demelier demelier.da...@gmail.com mailto:demelier.da...@gmail.com wrote: Hello, I've just realized that libsndfile is required for musicpd. see : $ ldd /usr/local/bin/musicpd ... libFLAC.so.10 = /usr/local/lib/libFLAC.so.10 (0x802331000) libsndfile.so.1 = /usr/local/lib/libsndfile.so.1 (0x802468000) libaudiofile.so.0 = /usr/local/lib/libaudiofile.so.0 (0x8025d1000) ... And : $ pkg_info -R libsndfile-1.0.24 Information for libsndfile-1.0.24: Required by: sfml-1.6 It seems that musicpd implicitly link to libsndfile if it is installed on the system. May I propose a PR with a new option to disable/enable this linkage using an OPTION? Thank you, that would be most welcome. I would do it myself, but I think you'll be quicker at the moment... Chris Thanks for your quick reply :-) There is the patch : http://www.freebsd.org/cgi/query-pr.cgi?pr=158999 -- David Demelier ___ 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
Xfce 4.8 updates synchronized with latest snapshot of marcuscom.com repository
Hi, I've just created tarball [1] with latest updates of Xfce 4.8 (core). Archive is synchronized with latest snapshot of marcuscom repository (GNOME). If you intend to test this: 1. Copy the Mk/bsd.xfce.mk (from mc_xfce-4.8.tar.bz2) 2. Upgrade Xfce components, following this order: - devel/xfce4-dev-tools - x11/libxfce4util - x11/xfce4-conf - x11/libxfce4menu - glade3 - x11-toolkits/libxfce4gui - glade3 - x11/libexo - http://www.FreeBSD.org/cgi/query-pr.cgi?pr=157768 - sysutils/garcon - http://www.FreeBSD.org/cgi/query-pr.cgi?pr=158144 - deskutils/xfce4-tumbler - poppler - x11-wm/xfce4-panel - http://www.FreeBSD.org/cgi/query-pr.cgi?pr=158148 - x11-fm/thunar - libexo, libnotify - sysutils/xfce4-settings - libexo, libnotify - x11-wm/xfce4-session - panel - x11-wm/xfce4-desktop - garcon, libnotify - x11-wm/xfce4-wm - sysutils/xfce4-utils - http://www.FreeBSD.org/cgi/query-pr.cgi?pr=158145 - misc/xfce4-appfinder - garcon - x11-themes/gtk-xfce-engine - deskutils/xfce4-notifyd - libexo, libnotify - x11/Terminal - http://www.FreeBSD.org/cgi/query-pr.cgi?pr=158170 - deskutils/orage - clean pkg-plist - x11-fm/thunar-vfs - libnotify In tarball, you can find also x11-fm/thunar-devel (v1.3.0 instead of v1.2.x), and patches for audio/thunar-media-tags-plugin [2]. If you use devel/py-notify with gtk-2.24.5, you needed to fetch a patch [3]. If you want to clone, my repository, be careful, I use my own Mk/bsd.xfce.mk (I introduce a new macro, 'xfcehack', which affect orage, Thunar, xfce4-session, panel, and Thunar plugins), choose '4.8_mc' branch. [1] http://code.google.com/p/xfce-ports/downloads/list [2] http://www.FreeBSD.org/cgi/query-pr.cgi?pr=157092 [3] http://code.google.com/p/olivier-freebsd-ports/source/browse/#hg%2Fdevel%2Fpy-notify -- olivier ___ 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: comms/umcs7840 doesn't compile under FreeBSD 8.2-stable
Hello, Torfinn. You wrote 17 июля 2011 г., 16:47:44: I just upgraded my machine to FreeBSD 8.2-stable (it was running 8.1-stable before): tingo@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 Known problem, as FreeBSD 8.2-STABLE change ABI for USB modules at some point without any indication, so there is no way to distinguish these FreeBSD versions.. But here is good news: driver is in base system now, simple kldload umcs.ko does job :) OR add load_umcs=YES into /boot/loader.conf -- // Black Lion AKA Lev Serebryakov l...@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: Submitting a follow up to a port update
-Original Message- From: owner-freebsd-po...@freebsd.org [mailto:owner-freebsd- po...@freebsd.org] On Behalf Of Chris Rees Sent: Saturday, 16 July 2011 11:33 AM To: ga...@16degrees.com.au Cc: skreu...@freebsd.org; freebsd-ports@freebsd.org Subject: Re: Submitting a follow up to a port update On 12 July 2011 23:38, Gavin McDonald ga...@16degrees.com.au wrote: Hi All, I'm the current maintainer for the scons port. http://www.freebsd.org/cgi/query-pr.cgi?pr=158205 As you can see, on the 24th June an update/patch was requested. I also received 2 emails, one from skreuzer via FreeBSD-gnats-submit and then also one from Edwin via bug-followup. So I check it out etc, looks fine and I want to approve it. So what did I do I clicked on the 'Submit Followup' link on the webpage (mailto:bug- follo...@freebsd.org,skreu...@freebsd.org?subject=Re:%20po rts/15 8205:%20%5BPATCH%5D%20devel%2Fscons%3A%20update%20to%20%32.% 30.%31) I send my email there and to 'bug-follo...@freebsd.org'; 'skreu...@freebsd.org' on the 25th June. Not only have I not heard anything but my follow up and approval to patch has not appeared on the patch [158205] I assume I have done something wrong? I also assume folks think I have been ignoring them and will get ousted by a maintainer timeout when in fact I replied approving the patch after only one day. What do I need to do now? Thanks Gav... pgollucci@ has just fixed it for you. All you have to do is wait for skreuzer@ to commit it ;) Chris Great, thanks Chris, Philip and skreuzer :) Gav... ___ 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
