Handing references to GPL within ports
I'm working on a port for H-Inventory (a computer inventory/resource management tool). By default, it installs a copy of the GPL. According to the Porter's Handbook, a port should avoid installing copies of the GPL. Whilst it's fairly easy to adapt the port so it doesn't install the license file, the installed web pages include at least one hyperlink to the file (I haven't done a complete check). What is the preferred mechanism for handling this? - Ignore the Porter's Handbook and install the file anyway - Create a symlink to an existing copy of the GPL. (In which case, where do I find a GPL that will always exist) - Change the hyperlink to point to a copy of the GPL on the Internet - something else. -- Peter Jeremy pgpatj6iGnCSs.pgp Description: PGP signature
When PHP5 port will be updated?
Hi, PHP 5.2.4 has been released three weeks ago, but still is not available for FreeBSD (5.2.3 is the latest portversion) http://www.freebsd.org/cgi/query-pr.cgi?pr=116182 According to the above pr, PHP 5 versions before 5.2.4 have numerous security vulnerabilities that have been addressed with the latest version. I've heared that the cause of the delay is the lack of a compatible Suhosin patch. Same happened months ago with a previous php5 release. If this is the reason of delay, then please split the port in two new ones, with and without Suhosin. Any idea when the updated php5 port will be released? Ted ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
configure editors/vim
Hi! I'm a developer using gvim with it's tagging through exctags (somehow ctags never worked for me). As vim port have no configuration options, it can't be configured easyly through 'make config'. I'm too lazy for digging Makefile for options every time I compile new version of vim, I added configuration options to Makefile. I'm new to FreeBSD, also to it's Ports, so maybe I don't see the reasons, these options aren't in the Makefile, but maybe they should be there. Anyway, I attach my change, maybe it will be acceptable to have it's way to ports. And if not, maybe it will help for someone else too :) EdE [EMAIL PROTECTED] /usr/ports/editors/vim]# diff -u Makefile.orig Makefile --- Makefile.orig Thu Sep 13 13:52:20 2007 +++ MakefileThu Sep 13 13:52:27 2007 @@ -29,6 +29,17 @@ SLAVEDIRS= editors/vim-lite +OPTIONS= PERL Enable Perl interpreter off \ + PYTHON Enable Python interpreter off \ + RUBY Enable Ruby interpreter off \ + CSCOPE Enable cscope off \ + EXUBERANT_CTAGS Use exctags instead of ctags off \ + ATHENA Athena GUI off \ + GTK2 GTK2 GUI off \ + GNOME Gnome1 GUI off \ + MOTIF Motif GUI off \ + XTERM_SAVE off + .if defined(PACKAGE_BUILDING) !defined(LITE) #WITH_TCL= yes WITH_PERL= yes ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: When PHP5 port will be updated?
In response to Robert Huff [EMAIL PROTECTED]: Ted Nicolson writes: Any idea when the updated php5 port will be released? When the maintainer has time to work on it and decided it's ready. Alternately, you could submit a patch. While you're welcome to post FreeBSD-related email of just about any nature, you're posting is not (generally) conducive to getting things done in the Open Source world. The following improvements will likely lead to better responses in the future. * [EMAIL PROTECTED] is listed as the maintainer for this port. By emailing ports@, you show that you haven't done any real research into the situation. It would be appropriate to email ale@ first to check on the status, and only email ports@ if ale@ doesn't respond. * You email comes across as rather demanding. While that may not have been your intent, that's how it reads. Demanding things of volunteers usually doesn't win you a lot of friends. Consider using phrases like, is there any way I can help speed up the process It's quite possible that ale@ is working on it, and having some testers would be helpful to him. -- Bill Moran http://www.potentialtech.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: When PHP5 port will be updated?
On Thu 13 Sep 2007 20:09, LI Xin wrote: Ted Nicolson wrote: Hi, PHP 5.2.4 has been released three weeks ago, but still is not available for FreeBSD (5.2.3 is the latest portversion) http://www.freebsd.org/cgi/query-pr.cgi?pr=116182 According to the above pr, PHP 5 versions before 5.2.4 have numerous security vulnerabilities that have been addressed with the latest version. I've heared that the cause of the delay is the lack of a compatible Suhosin patch. Same happened months ago with a previous php5 release. If this is the reason of delay, then please split the port in two new ones, with and without Suhosin. Any idea when the updated php5 port will be released? I think ale@ is working on it, plus some new proposed changes in our PR database. Because php5 is a widely used port so he may want to test it for more time. Cheers, -- Xin LI [EMAIL PROTECTED]http://www.delphij.net/ FreeBSD - The Power to Serve! If you really want to update php to 5.2.4 you can use this patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/116188 Note that I wouldn't recommend using this patch, the security issues in 5.2.3 are not very serious, and this patch doesn't include the Suhosin patch. Regards, Martin Tournoij ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: configure editors/vim
On Thu 13 Sep 2007 14:09, Gergely S�nta wrote:
Hi!
I'm a developer using gvim with it's tagging through exctags (somehow ctags
never worked for me). As vim
port have no configuration options, it can't be configured easyly through
'make config'. I'm too lazy for
digging Makefile for options every time I compile new version of vim, I added
configuration options to
Makefile.
I'm new to FreeBSD, also to it's Ports, so maybe I don't see the reasons,
these options aren't in the
Makefile, but maybe they should be there. Anyway, I attach my change, maybe
it will be acceptable to have
it's way to ports. And if not, maybe it will help for someone else too :)
EdE
[EMAIL PROTECTED] /usr/ports/editors/vim]# diff -u Makefile.orig Makefile
--- Makefile.orig Thu Sep 13 13:52:20 2007
+++ MakefileThu Sep 13 13:52:27 2007
@@ -29,6 +29,17 @@
SLAVEDIRS= editors/vim-lite
+OPTIONS= PERL Enable Perl interpreter off \
+ PYTHON Enable Python interpreter off \
+ RUBY Enable Ruby interpreter off \
+ CSCOPE Enable cscope off \
+ EXUBERANT_CTAGS Use exctags instead of ctags off \
+ ATHENA Athena GUI off \
+ GTK2 GTK2 GUI off \
+ GNOME Gnome1 GUI off \
+ MOTIF Motif GUI off \
+ XTERM_SAVE off
+
.if defined(PACKAGE_BUILDING) !defined(LITE)
#WITH_TCL= yes
WITH_PERL= yes
You should send these kind of questions/suggestions to the port
maintainer, not to the ports mailing list.
I've cc-ed the port maintainer in this email.
Some general tips on port knobs:
You can use:
grep WITH Makefile
To get a list of knobs, which is easier than viewing the Makfile with
less.
You can use /etc/make.conf to specify default port knobs, here's my
vim configuration in /etc/make.conf:
.if ${.CURDIR:M*/editors/vim}
WITHOUT_X11=yes
NO_GUI= yes
.if exists(/phong)
WITH_PERL= yes
WITH_PYTHON=yes
WITH_CSCOPE=yes
.elif exists(/glitch)
WITHOUT_PERL= yes
.endif
.endif
The files /glitch and /phong are used to identify which machine we're
running on, and adjust the knobs accordingly.
Regards,
Martin Tournoij
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: When PHP5 port will be updated?
I will update the port tomorrow. Yes, testing things requires time. Yes, I'm working on a few PRs. Yes, I was waiting for suhosin since it's on by default. Yes (even if nobody said it), using php 5.2.4 without suhosin is more dangerous than php 5.2.3 with suhosin. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Handing references to GPL within ports
On Sep 13, 2007, at 12:21 AM, Peter Jeremy wrote: I'm working on a port for H-Inventory (a computer inventory/resource management tool). By default, it installs a copy of the GPL. According to the Porter's Handbook, a port should avoid installing copies of the GPL. Whilst it's fairly easy to adapt the port so it doesn't install the license file, the installed web pages include at least one hyperlink to the file (I haven't done a complete check). What is the preferred mechanism for handling this? - Ignore the Porter's Handbook and install the file anyway - Create a symlink to an existing copy of the GPL. (In which case, where do I find a GPL that will always exist) - Change the hyperlink to point to a copy of the GPL on the Internet - something else. It wouldn't hurt to install the file anyway, but if you'd like to try to following the Porter's Handbook recommendations more closely, making a symlink to /usr/src/gnu/COPYING is going to provide you with the GPLv2 license text, presuming /usr/src is available on the machine in question. I don't think the third option is a good idea-- if the license for the software requires one to make the license text available, then it should be available from the same machine which the software is on. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: cvs commit: ports/Mk bsd.port.mk bsd.xorg.mk ports UPDATING ports/x11-drivers/xf86-input-acecad Makefile distinfo ports/x11-drivers/xf86-input-calcomp Makefile distinfo ports/x11-drivers/xf86-in
FYI. If you're experiencing any issue, please send detailed reports to [EMAIL PROTECTED] Original Message Subject: cvs commit: ports/Mk bsd.port.mk bsd.xorg.mk ports UPDATING ports/x11-drivers/xf86-input-acecad Makefile distinfo ports/x11-drivers/xf86-input-calcomp Makefile distinfo ports/x11-drivers/xf86-input-citron Makefile distinfo ... Date: Thu, 13 Sep 2007 19:45:43 + (UTC) From: Florent Thoumie [EMAIL PROTECTED] To: [EMAIL PROTECTED] flz 2007-09-13 19:45:08 UTC FreeBSD ports repository Log: - Update X.org ports to 7.3. - Mark XFree86-4 as DEPRECATED with EXPIRATION_DATE set to 2007-12-25. I hope that nobody will be bored enough on Christmas to remove them on that day. Tested by: vehemens, Rene Ladan, Beech Rintoul, sarek on x11@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A new version of Tools/scripts/plist
On Mon 10 Sep 2007 12:09, Jeremy Messenger wrote: On Mon, 10 Sep 2007 03:31:08 -0500, Martin Tournoij [EMAIL PROTECTED] wrote: I've written a replacement for /ports/Tools/scripts/plist, the reason this is a complete rewrite rather than an update is because I'm not familair with ruby, and writing a new version in python was faster. Problems/additions in this rewrite: - Automaticlly replace the default PLIST_SUB values. - Sensible sorting of the directory list, the current plist put directory's in ths order: share/someport/ share/someport/adir/ share/someport/adir/foobar Which is the reverse of what it should be. - There are a number of directory's which are always created but should not be added to the pkg-plist, I have no idea where these directory's come from, see the comment on line 49 of my script. I wrote this script for personal purposes, but why not let other people benefit, maybe it can be placed in Tools/scripts? Either replacing the current plist or alongside it. Script is attached in this email, or you can view it online if you like: http://www.rwxrwxrwx.net/plist.py.txt I haven't use it, but I noticed that the mtree needs to be update to /usr/ports/Templates/BSD.local.dist and we don't use BSD.x11.dist any longer. I think it's safe for you to remove that workaround. I think you should go with 'make -V MTREE_FILE' instead of hardcore. You can check auto-plist[1] that I have written to get idea/copy and improvement in your one. [1] http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/portstools/auto-plist/ Cheers, Mezz Regards, Martin Tournoij Hello Mezz, Thanks for the tip on mtree file, somehow my grepping of /ports/Mk/* didn't find it. Your auto-plist script seems to be more or less the same as my script, I wasn't aware of it's existence ... Ah well, you can never have to many scripts I suppose... Regards, Martin Tournoij ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
qemu-launcher crash under RELENG_6
I've had at least one person report a crash on RELENG_6 for a port I maintain. I've been trying to track down the exact cause but I can't seem to find it. Clicking any open button in qemu-launcher (emulators/qemu-launcher) results in the following: /libexec/ld-elf.so.1: /usr/local/lib/libgthread-2.0.so.0: Undefined symbol pthread_getschedparam Searching around I've come to believe that something is using the wrong threading library but I'm at a loss as to what it could be or how to find it. Any suggestions? -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu-launcher crash under RELENG_6
On Thu 13 Sep 2007 16:09, Wesley Shields wrote: I've had at least one person report a crash on RELENG_6 for a port I maintain. I've been trying to track down the exact cause but I can't seem to find it. Clicking any open button in qemu-launcher (emulators/qemu-launcher) results in the following: /libexec/ld-elf.so.1: /usr/local/lib/libgthread-2.0.so.0: Undefined symbol pthread_getschedparam Searching around I've come to believe that something is using the wrong threading library but I'm at a loss as to what it could be or how to find it. Any suggestions? -- WXS The correct threading library is used, and the problem doesn't seem to have anything to do with qemu-launcher. I'm guessing it's caused by incompatible or incorrect updates, try deinstalling and rebuilding glib2, gtk2, p5-glib2, and p5-gtk2. Be sure to csup the ports tree first. Regards, Martin Tournoij ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: qemu-launcher crash under RELENG_6
On Fri, Sep 14, 2007 at 01:58:20AM +0200, Martin Tournoij wrote: On Thu 13 Sep 2007 16:09, Wesley Shields wrote: I've had at least one person report a crash on RELENG_6 for a port I maintain. I've been trying to track down the exact cause but I can't seem to find it. Clicking any open button in qemu-launcher (emulators/qemu-launcher) results in the following: /libexec/ld-elf.so.1: /usr/local/lib/libgthread-2.0.so.0: Undefined symbol pthread_getschedparam Searching around I've come to believe that something is using the wrong threading library but I'm at a loss as to what it could be or how to find it. Any suggestions? -- WXS The correct threading library is used, and the problem doesn't seem to have anything to do with qemu-launcher. I'm guessing it's caused by incompatible or incorrect updates, try deinstalling and rebuilding glib2, gtk2, p5-glib2, and p5-gtk2. Be sure to csup the ports tree first. I know it has nothing to do with qemu-launcher. The thing is that I did nothing out of the ordinary for this and it is a fresh install in a VM. I installed 6.2, updated to RELENG_6, built xorg and gnome2 then qemu-launcher all from ports in that order and this is the result. I'll try rebuilding them all again tomorrow but I'm not thinking it will make a difference. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[headsup] latest changes to bsd.perl.mk, and regressions
This should fix the remaining perl-related problems that people were seeing, each related to ports that conditionally included perl. The only remaining regressions that I can't yet explain are the following: */fpc-* fail to compile due some kind of flag failure. (They work on my 6.2 machine here). lang/dylan does not seem to build reliably. */hs-* are refusing to install. Someone's going to need to help me out with these. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
djbdns
Hi folks, I'm having issues building djbdns; I'm not able to download any of the tarballs from the sources listed in Makefile. Is this issue known, or is it just something affecting me? Thanks! James ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: djbdns
On Thu, Sep 13, 2007 at 07:51:21PM -0600, James wrote: I'm having issues building djbdns; I'm not able to download any of the tarballs from the sources listed in Makefile. Is this issue known, or is it just something affecting me? Can you give us some logs? Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap fetch bug or quality
Alexander Sizov wrote: The number of fetching patches (1980) != number of fetched patches (143[8-9]). Why it happens? Does it happen only on portsnap3, right? Yes. I dunno why, but portsnap3 had strange behaviors since the beginning. Apart from speed (it's the slowest from here), I always had disconnections and errors when fetching many (hundreds) updates, and recently I saw also the very same mismatch: I thought about another premature disconnection, but no, it fetched all the updates even if the number was incorrect. Perhaps Colin can give us an explanation. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
