Re: powerdns is marked as broken in FreeBSD
Oops! same as powerdns-recursor Is there anyway to downgrade it ? On 5 November 2016 at 12:23, Bill Yuan <byc...@gmail.com> wrote: > #pwd > /usr/ports/dns/powerdns > #make > ===> powerdns-4.0.1 is marked as broken on FreeBSD 9.3: Does not link. > *** [all] Error code 1 > > Stop in /usr/ports/dns/powerdns > # > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
powerdns is marked as broken in FreeBSD
#pwd /usr/ports/dns/powerdns #make ===> powerdns-4.0.1 is marked as broken on FreeBSD 9.3: Does not link. *** [all] Error code 1 Stop in /usr/ports/dns/powerdns # ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: binutils 2.27 [not working for powerpc64 (and powerpc?)]
I don't have a massive amount expertise in this area but I'll look into it. >From what I can tell this seems to only affect powerpc64. Bill On Tue, Sep 20, 2016 at 4:55 PM, Mark Millard <mar...@dsl-only.net> wrote: > > On 2016-Sep-20, at 1:59 PM, Dimitry Andric wrote: > > > Has anyone succeeded in bisecting upstream binutils, to see where this > problem was introduced? > > > > -Dimitry > > Apparently not from what I've seen in the lists. It will be a couple/few > weeks before I again have powerpc64 or powerpc access. I've just been > monitoring powerpc64 & powerpc things in hopes of things working once I > have access again --or at least my knowing what to do to sidestep issues > and what sequence to progress in from what I had in very early 2016-June > when I lost access temporarily. > > May be someone will have the time & knowledge to bisect the upstream > binutils materials. I may figure how to sometime after I get access again. > But it is not the only FreeBSD powerpc64 (PowerMac) thing that I'd likely > be investigating. (Example: because of problems with sprg0-value handling > for FreeBSD vs. OpenFirmware on PowerMac powerpc64's: testing usefdt=1 mode > for Nathan Whitehorn in hopes of future changes avoiding OpenFirmware use > from FreeBSD. Nathan put the hooks in place for testing somewhat after I'd > already lost access.) > > I wonder if the various(?) binutil port(s) that are 2.27 based now and can > be built to target powerpc64/powerpc should be marked broken for > powerpc64/powerpc until this is figured out. Any ports that are only for > targeting powerpc64 or powerpc probably should not be at 2.27 at this point. > > I've submited a bugzilla report 212868 for devel/binutils with the text of > the list reports that I've quoted. > > > > On 20 Sep 2016, at 22:56, Mark Millard wrote: > >> > >> The below forward from freebsd-pcc's list confirms that binutils 2.27 > not working for powerpc64 (& powerpc?) contexts. > >> > >> Note: Krzysztof Parzyszek is one of the two people that have recently > been working on updating clang/llvm for fixing some of the issues that > block FreeBSD from using clang for powerpc and powerpc64 for buildworld and > buildkernel. > >> > >> === > >> Mark Millard > >> markmi at dsl-only.net > >> > >> On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek swissmail.org> wrote: > >> > >>> I've had similar problems after building gcc-4.8. After reverting > back to binutils 2.25 and rebuilding, it worked fine. > >>> > >>> -Krzysztof > >>> > >>> On 9/9/2016 11:32 AM, Bill Sorenson wrote: > >>>> Everything I've built with the new binutils using either GCC 4.9, 5.4 > or > >>>> 6.2 instantly dumps when run. This is on an Xserve G5. Is this just > me or > >>>> is there something genuinely broken here? > >>>> > >>>> Thanks, > >>>> Bill > > > === > Mark Millard > markmi at dsl-only.net > > ___ > freebsd-toolch...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to "freebsd-toolchain- > unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PostgreSQL server bus error with uuid-ossp extension
On Mon, 7 Oct 2013 11:20:23 +0800 Christopher Hall christopherhall@gmail.com wrote: Hello Bill, On Fri, 4 Oct 2013 08:34:35 -0400 Bill Moran wmo...@potentialtech.com wrote: On Fri, 4 Oct 2013 15:44:51 +0800 Christopher Hall christopherhall@gmail.com wrote: When running PostgreSQL with the uuid-ossp extension the server fails with signal 10 (bus error). http://pgfoundry.org/projects/uuid-freebsd/ Thanks for the information. I would sooner stay with the existing module so as to be compatible with Linux. Currently I am trying out a patch to misc/uuid-ossp so I can just compile the postgres-contrib unmodified. uuid-freebsd is intended to be compatable. What are you finding incompatable? Although I would be appreciative if you could get that patch working. -- Bill Moran wmo...@potentialtech.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: PostgreSQL server bus error with uuid-ossp extension
On Fri, 4 Oct 2013 15:44:51 +0800 Christopher Hall christopherhall@gmail.com wrote: When running PostgreSQL with the uuid-ossp extension the server fails with signal 10 (bus error). http://pgfoundry.org/projects/uuid-freebsd/ -- Bill Moran wmo...@potentialtech.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
Can I get some love on this PR?
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168583 This bugger is about a month old at this point. Of course, part of that is my fault for being slow to respond, so I'm just putting a heads-up out -- if anyone is able to commit that, it'd be great. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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 py27-openssl-0.13 bugs
Hello, I am having problems with this port (py27-openssl-0.13) on FreeBSD 7 (Freenas 0.7.2 - 8191) from OpenSSL import SSL returns: Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python2.7/site-packages/OpenSSL/__init__.py, line 41, in module from OpenSSL import rand, SSL ImportError: /usr/local/lib/python2.7/site-packages/OpenSSL/SSL.so: Undefined symbol SSL_get_servername I am trying to use it for SSL with sabnzbd, and found others are having the same issue: http://forums.sabnzbd.org/viewtopic.php?t=9425 I am not a developer, but if I can help in any way with testing, etc please let me know. 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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: textproc/uni2ascii build failure on FreeBSD 7.3
Alternatively, one could try and get the author (CC'd) to restore getline.c in the official source but only build it/make use of it when a specific configure or make flag is specified. Hi. I think that's the best solution. I'll restore the internal copy and test for the library version in the configure file. ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Fw: VirtualBox coredump on FreeBSD 8 during build
I sent the information to the maintainer but haven't heard back yet. Don't know how busy they are, or if they're on holiday or whatever. In any event, I'm reposting this here, in the hopes that someone else has seen this problem and can make a recommendation. Begin forwarded message: Date: Tue, 9 Mar 2010 20:33:48 -0500 From: Bill Moran wmo...@potentialtech.com To: v...@freebsd.org Subject: VirtualBox coredump on FreeBSD 8 during build FreeBSD monster 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #3: Sun Dec 13 14:53:34 EST 2009 r...@monster:/usr/obj/usr/src/sys/GENERIC i386 Ports tree updated as of an hour or so ago. I get the following error doing make install: [r...@monster /usr/ports/emulators/virtualbox-ose]# make install clean === virtualbox-ose-3.1.2_1 depends on executable: yasm - found === virtualbox-ose-3.1.2_1 depends on executable: as86 - found === virtualbox-ose-3.1.2_1 depends on executable: xsltproc - found === virtualbox-ose-3.1.2_1 depends on executable: kmk - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/easy_install-2.5 - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/python2.5 - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/libdata/pkgconfig/xcursor.pc - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/libdata/pkgconfig/xmu.pc - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/lib/qt4/libQtGui.so - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/linguist-qt4 - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/moc-qt4 - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/lib/qt4/libQtNetwork.so - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/rcc - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/uic-qt4 - found === virtualbox-ose-3.1.2_1 depends on file: /usr/local/bin/sdl-config - found === virtualbox-ose-3.1.2_1 depends on executable: pkg-config - found === virtualbox-ose-3.1.2_1 depends on shared library: png.5 - found === virtualbox-ose-3.1.2_1 depends on shared library: xslt.2 - found === virtualbox-ose-3.1.2_1 depends on shared library: curl.5 - found === virtualbox-ose-3.1.2_1 depends on shared library: dbus-1.3 - found === virtualbox-ose-3.1.2_1 depends on shared library: SDL-1.2.11 - found === virtualbox-ose-3.1.2_1 depends on shared library: glib-2.0.0 - found === virtualbox-ose-3.1.2_1 depends on shared library: IDL-2.0 - found === Configuring for virtualbox-ose-3.1.2_1 Checking for environment: Determined build machine: freebsd.x86, target machine: freebsd.x86, OK. Checking for kBuild: found, OK. Checking for gcc: found version 4.2.1, OK. Checking for as86: found version 0.16.17, OK. Checking for bcc: found version 0.16.17, OK. Checking for iasl: found version 20090521, OK. Checking for xslt: found, OK. Checking for pthread: found, OK. Checking for libxml2: found version 2.7.6, OK. Checking for libxslt: found version 1.1.26, OK. Checking for libIDL: found version 0.8.13, OK. Checking for ssl: found version OpenSSL 0.9.8k 25 Mar 2009, OK. Checking for libcurl: found version 7.19.7, OK. Checking for zlib: found version 1.2.3, OK. Checking for SDL: found version 1.2.14, OK. Checking for X libraries: found, OK. Checking for Xcursor: found, OK. Checking for Xmu: found, OK. Checking for Mesa / GLU: Segmentation fault (core dumped) === Script configure failed unexpectedly. Please report the problem to v...@freebsd.org [maintainer] and attach the /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.2_OSE/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. I'd love to send the file requested, however, there is no such file. If the solution isn't immediately obvious, let me know what debugging steps I can take to help sort this out. Follows the output of pkg_info: [r...@monster /usr/ports/emulators/virtualbox-ose]# pkg_info ORBit2-2.14.17 High-performance CORBA ORB with support for the C language OpenEXR-1.6.1_2 A high dynamic-range (HDR) image file format Terminal-0.4.3_1Terminal emulator for the X windowing system Thunar-1.0.1_3 XFce 4 file manager a2ps-letter-4.13b_4 Formats an ascii file for printing on a postscript printer aalib-1.4.r5_4 An ascii art library amspsfnt-1.0_5 AMSFonts PostScript Fonts (Adobe Type 1 format) appres-1.0.1Program to list application's resources aspell-0.60.6_2 Spelling checker with better suggestion logic than ispell atk-1.28.0 A GNOME accessibility toolkit (ATK) autoconf-2.62 Automatically configure source code on many Un*x platforms autoconf-wrapper-20071109 Wrapper script for GNU autoconf automake-1.9.6_3GNU
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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: [Firefox] Why we can't update..
On 1/23/10 3:02 PM, Doug Barton wrote: On 01/23/10 10:16, Martin Wilke wrote: Before we get more mails with the question why we not update firefox to 3.6, the answer is easy, nox@ found some problems with some plugins, this problem seems to be only FreeBSD releated under Linux or Windows seems to be works all fine. Some plugins crash with some open ASSERTS, we working on this problem but that need a bit time. So please wait a bit. Thanks! No no, thank YOU. :) I was going to report that moving from RC1 to RC2 caused me a lot of problems, but nice to know that y'all are on the case. FWIW I have the following plugins installed, downloaded from addons.mozilla.org: Ditto. Sometimes I forget to thank folks for all the hard work they do. In this case, thank you for: 1) Maintaining this port 2) Making sure things work before you update and 3) Taking the time to give everyone a heads-up about what's going on. -Bill ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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: Need advice from maintainers
In response to Paul Schmehl pschmehl_li...@tx.rr.com: I am the maintainer for security/barnyard2. This is an updated version of security/barnyard, which I also maintain. The version of my port is the current release version, but it has a really irritating problem that is fixed in the current beta version. Barnyard2 is a program that parses snort logs and inserts them into a database (mysql or postgresql). It is supposed to create a placemarker file (called a waldo file) that maintains a record of what logs it has already parsed. (This is only one way of using the program. There are others as well.) The problem in the release version is that it does not read the waldo file when the program is restarted. So every time you restart barnyard2, it reinserts into the database every alert you still have log files for. The beta version fixes this problem. I have created a port for the beta version and am using it myself, but I know that using beta versions of software is frowned upon. Should I go ahead and submit this port because it solves this problem? If I do, my thinking is that I should adjust the pkg-message file in the existing port to warn the user about the problem and note that the beta version solves it so they might want to consider using that instead. An option that you did not mention is to take the patch that fixes that single problem and include as a patch file for barnyard2. That way it's not a true beta, it just has that single patch to fix a known problem. For me, I think that would be the preferred method in this case. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: Need advice from maintainers
In response to Paul Schmehl pschmehl_li...@tx.rr.com: --On Wednesday, October 21, 2009 10:31:21 -0500 Bill Moran wmo...@potentialtech.com wrote: In response to Paul Schmehl pschmehl_li...@tx.rr.com: I am the maintainer for security/barnyard2. This is an updated version of security/barnyard, which I also maintain. The version of my port is the current release version, but it has a really irritating problem that is fixed in the current beta version. Barnyard2 is a program that parses snort logs and inserts them into a database (mysql or postgresql). It is supposed to create a placemarker file (called a waldo file) that maintains a record of what logs it has already parsed. (This is only one way of using the program. There are others as well.) The problem in the release version is that it does not read the waldo file when the program is restarted. So every time you restart barnyard2, it reinserts into the database every alert you still have log files for. The beta version fixes this problem. I have created a port for the beta version and am using it myself, but I know that using beta versions of software is frowned upon. Should I go ahead and submit this port because it solves this problem? If I do, my thinking is that I should adjust the pkg-message file in the existing port to warn the user about the problem and note that the beta version solves it so they might want to consider using that instead. An option that you did not mention is to take the patch that fixes that single problem and include as a patch file for barnyard2. That way it's not a true beta, it just has that single patch to fix a known problem. For me, I think that would be the preferred method in this case. I *might* be able to do that, if I can figure out where in the code the problem is fixed. I've had two semesters of C++, but I am not a programmer and consider myself the rankest of novices wrt code. In a perfect world. you wouldn't have to be a C++ coder. In theory, you should be able to look at their SVN/CVS/git/whatever repository and find the commit that says it's fixed this problem, then just generate a diff between that version and the release version. Of course, that's in a perfect world. I'm not familiar with that project, so I don't know if they're that organized or not. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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: Signing Request
In response to J. Hellenthal jhellent...@gmail.com: If you do not need to pgp/gpg sign email message to the lists please don't. What is the purpose of your message? The above statement is self-cancelling. If I go to the trouble to establish a pgp/gpg key, I will sign every single message that I send out. The purpose of this is to differentiate actual messages from me from messages that may impersonate me. I know I probably don't have your pgp public key and a lot more users probably do not either. Please use your best judgment. While you're free to voice your opinion, I don't understand your purpose in spamming three mailing lists with this demand. What problem are you trying to solve? -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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: Multiple instances of Mailman on FreeBSD
In response to Jeffrey Goldberg jeff...@goldmark.org: I'm posting this to both the mailman-users list and the freebsd-ports list. I realize that not all follow-up will make it to both lists. I would like to set up multiple instances of Mailman on a FreeBSD 7- STABLE system with using Postfix. Looking at the ports Makefile, it appears that if I set MM_DIR=mailman/vhosts/domain-for-this-instance everything should work file (plus add FORCE_PACKAGE_REGISTER allow this second instance to be installed.) Were it me, I'd add jails to the system. Then you can install a separate copy of mailman in each jail. This will keep them happily independent of each other. That's obviously not the only way to get what you want, just my suggestion. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
offer laptop accessory Code:44
To: Purchase Dept I am very happy to know you from website http://www.chruetertee.ch; that you are doing business of laptop parts. This is Bill from HongKong Flier Developers Co.,Limited, a reputed supplier of laptop battery. Now we are able to provide more than 250pcs batteries for different models, developing new models every month. We have put much importance to quality control and service, so with low RMA. Besides replacement laptop battery, we also have a wide and stable source for original/genuine memory, laptop batteries, laptop adapters. I would like to provide detailed pricelists if you request, and hope that we have chance to do lots of business in the future. We apologize for any inconviences if you are not interested in the offer! Thank you! Have a nice day! Bill Luo (Sales Supervisor) HongKong Flier Developers Co.,Limited Tel: +86-755-2828 4807Fax: +86-755-8957 8417 www.flierdevelopers.com b...@flierdevelopers.com billfl...@hotmail.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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
A plea or sanity in port options menu
I don't believe this is particularly useful: Options for port-fu [ ] BRG Enable BRG support [X] QFZ Enable QFZ support Quite honestly, if you can't figure out that checking the box next to BRG enables BRG support, then don't use a computer. However, if you don't already know what BRG _is_, then those menus are worthless gobbly-gook. So, you've held my hand long enough to teach me that putting an X in a box enables something, but you've given me absolutely NO idea what I've actually done. How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. This is so common in the ports infrastructure, that I'm sure a bazillion maintainers are going to scream at me for complaining about it. After all, _everyone_ else does the same thing. But it's completely worthless to have the description simply repeat what the tag is. It's also really bad UI design. Quite honestly, it makes me wonder if the port creator was even awake when they typed up the Makefile. Please, please, please stop this. I'm floored by the pervasiveness of this insanity, and there's absolutely no reason for it to continue. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: A plea or sanity in port options menu
In response to Warren Block wbl...@wonkity.com: On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. There was talk some time ago of having extended descriptions. Several ideas, but the one that made the most sense to me would be a box at the bottom that would display a description as you moved through the options: [.] BRG [X] QFZ Bernstein Riggs Guillotine parsing with the . representing the cursor/highlight position. Move down and the bottom line would change to say Quantum Freeze Zulu rending. The nice thing about the box at the bottom is it would give a full line or possibly several lines for explanations. Seems like it could be added without breaking the existing system with an optional OPTIONS_DESC variable that would correspond with OPTIONS. I don't really know how hard that would be; ideas are cheap, implementation more costly. I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. A quick test of some ports turns up this one: [ ] OPENGL OpenGL support True but useless. How about: [ ] OPENGL Use OpenGL graphics library ...which, at least give the user _some_ idea what they're doing. OpenGL probably isn't a good example, however. It's pretty easy to Google OpenGL and figure out what it is. Here's some more bizarre options: [X] EPUB Epub modules [X] EXTENSIONSExtensions [X] TEMPLATE Templates [X] TOOLS Tools I mean, if I enable Extensions, what happens? How do I figure out what happens? I have to read the Makefile, at which point having these options on a menu is pretty pointless. I mean, I can't even come up with a Google search to help me figure out what tools are involved here. There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server) I mean, a Google on ICU is liable to bring up all sorts of medical drama websites, but I can do a search for ICU unicode and find my answer on the first result. Not only am I told that optimized compiler flags are an option, but I'm told the exact one that will be used (-O3) The porters handbook doesn't seem to offer any helpful advice on these: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html In fact, the examples it provides are excellent examples of doing it WRONG. Let me see about making a patch to the porters handbook to provide some advice ... -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is illogical layout of ports
Sokolov Alexey [EMAIL PROTECTED] wrote: Hi! The location of some ports contradictory. They need all rank in the categories you want. My goodness, you're right! Quick, stop all other development and have the entire FreeBSD community audit all _18000_ ports to ensure they're all in the appropriate categories! It shouldn't take long. I mean, there's no possibility that there'll be any disagreement among the community as to where each port belongs. There's no possibility that such an audit would be tied up in bikeshed discussions for eons. (Especially since I think most of the ports you complained about are already in the right place.) In all seriousness, what did you expect was going to happen as a result of your email? What did you really hope to accomplish? -- 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]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portupgrade xscreensaver-gnome
In response to Doug Barton [EMAIL PROTECTED]: Bill Moran wrote: It's a combination of a number of issues: 1) The ports infrastructure shouldn't let you set options that don't make sense. I think that one could argue that it should be _hard_ to set options that don't make sense, but I don't think it should be impossible. you have to keep in mind that we cater to a very diverse user community, from rank beginners to advanced hackers. True. My opinion: A GUI that _prevents_ novice users from selecting incompatible options is a good idea. Expert users can always manually tweak /var/db/ports/ files if they want to override those restrictions. 2) Why is portupgrade dying on a warning message? Why does a poor decision on one port prevent everything on my system from upgrading? For the same reason that portmaster dies on errors, neither program is omniscient. :) If ports tools hit a point where it's not clear how to proceed they _should_ stop and get user input. The next thing the users generally say is that it should somehow proceed with the rest of the upgrade, finish things that don't rely on the broken bits, etc. Unfortunately that is quite a bit harder to do than you might think, although patches are always welcome. Understood. But keep in mind that this was not an error, it was a warning. Perhaps the ports infrastructure doesn't differentiate between those two as much as I think. 3) The error from portupgrade does not immediately point me to the easy solution, it tricks me into thinking I have to hack the Makefile. I don't actually think that the error message you're referring to is from portupgrade, I think it's from the port itself. I can see that. -- 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]
Problems with portupgrade xscreensaver-gnome
cvsupped my ports tree just this morning. #uname -a FreeBSD vanquish.ws.pitbpa0.priv.collaborativefusion.com 7.0-RELEASE FreeBSD 7.0-RELEASE #4: Wed Jun 25 09:16:13 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VANQUISH i386 # pkg_info | grep portupgrade portupgrade-2.4.6,2 FreeBSD ports/packages administration and management tool s # portupgrade -a [...] ** Makefile possibly broken: x11/xscreensaver-gnome: Makefile, line 106: warning: Option KEYRING needs PAM, but PAM is disabled. xscreensaver-gnome-5.06_1 --- Session ended at: Wed, 30 Jul 2008 08:38:31 -0400 (consumed 00:01:10) /usr/local/sbin/portupgrade:1468:in `get_pkgname': Makefile broken (MakefileBrokenError) from /usr/local/sbin/portupgrade:622:in `main' from /usr/local/sbin/portupgrade:613:in `each' from /usr/local/sbin/portupgrade:613:in `main' from /usr/local/sbin/portupgrade:588:in `catch' from /usr/local/sbin/portupgrade:588:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `call' from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `parse_in_order' from /usr/local/lib/ruby/1.8/optparse.rb:1299:in `catch' ... 6 levels... from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize' from /usr/local/sbin/portupgrade:229:in `new' from /usr/local/sbin/portupgrade:229:in `main' from /usr/local/sbin/portupgrade:2208 If I comment out line 106 in that Makefile, all is fine. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portupgrade xscreensaver-gnome
In response to Marcin Wisnicki [EMAIL PROTECTED]: On Wed, 30 Jul 2008 08:51:23 -0400, Bill Moran wrote: cvsupped my ports tree just this morning. #uname -a FreeBSD vanquish.ws.pitbpa0.priv.collaborativefusion.com 7.0-RELEASE FreeBSD 7.0-RELEASE #4: Wed Jun 25 09:16:13 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/ sys/VANQUISH i386 # pkg_info | grep portupgrade portupgrade-2.4.6,2 FreeBSD ports/packages administration and management tool s # portupgrade -a [...] ** Makefile possibly broken: x11/xscreensaver-gnome: Makefile, line 106: warning: Option KEYRING needs PAM, but PAM is disabled. xscreensaver-gnome-5.06_1 You need to either enable PAM (recommended) or disable KEYRING by doing: cd /usr/ports/x11/xscreensaver-gnome/; make config Are you saying that I can't portupgrade ANY ports on my system until such time as I make this strange decision? Note that the message is a _WARNING_. So portupgrade is giving up on every port on my system because _one_ port has a warning? No, I tend to thing that something is wrong here. Should portupgrade bail because it sees a warning from a Makefile? -- 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: Problems with portupgrade xscreensaver-gnome
In response to Marcin Wisnicki [EMAIL PROTECTED]: On Wed, 30 Jul 2008 17:45:10 -0400, Bill Moran wrote: In response to Marcin Wisnicki [EMAIL PROTECTED]: On Wed, 30 Jul 2008 08:51:23 -0400, Bill Moran wrote: cvsupped my ports tree just this morning. #uname -a FreeBSD vanquish.ws.pitbpa0.priv.collaborativefusion.com 7.0-RELEASE FreeBSD 7.0-RELEASE #4: Wed Jun 25 09:16:13 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/ src/ sys/VANQUISH i386 # pkg_info | grep portupgrade portupgrade-2.4.6,2 FreeBSD ports/packages administration and management tool s # portupgrade -a [...] ** Makefile possibly broken: x11/xscreensaver-gnome: Makefile, line 106: warning: Option KEYRING needs PAM, but PAM is disabled. xscreensaver-gnome-5.06_1 You need to either enable PAM (recommended) or disable KEYRING by doing: cd /usr/ports/x11/xscreensaver-gnome/; make config Are you saying that I can't portupgrade ANY ports on my system until such time as I make this strange decision? Why do you think it is a strange decision? You have set non-default options that don't make sense and the port is warning you about that. Fixing it is quick, easy and painless. It's a combination of a number of issues: 1) The ports infrastructure shouldn't let you set options that don't make sense. If I can't use keyring without PAM, then why am I allowed to set such a thing. I believe such improvements to the ports structure are being worked on by others (based on other conversations I've seen on the list) so I won't belabour the point. 2) Why is portupgrade dying on a warning message? Why does a poor decision on one port prevent everything on my system from upgrading? 3) The error from portupgrade does not immediately point me to the easy solution, it tricks me into thinking I have to hack the Makefile. Anyway, I don't know what the correct solution is. I'm just pointing out the problem so that people smarter than me can work it out. I'm also presenting my viewpoint so those people know how confusing it was to me. Hope the information is helpful. -- 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]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
databases/evolution-data-server forces requirement on ldap
The port mentioned above has a hardcoded requirement to include openldap-client and does not obey WITHOUT_LDAP in /etc/make.conf (note that the mail/evolution port does obey WITHOUT_LDAP) I hacked the Makefile to remove the dependency and it seems to run fine. Haven't done extensive testing, but it seems as if a tweak to make it respect that setting would be nice. On a (possibly) related note, that port seems to require openldap-2.3 and the build breaks because I have openldap-2.4 installed. Unfortunately, I don't have time to investigate that now. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/mediawiki: PostgreSQL non functional - why? + texvc + dependencies
In response to Nikola Lečić [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 No answer after 15 days -- does this mean that the maintainer is not interested in this port? He could be on holiday or otherwise indisposed. Policy dictates that you should open this as a PR. If the PR sits longer than the maintainer timeout without a response from the maintainer, then other committers can make the change. There's documented policy on this: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/maintain-port.html - -- Nikola Lečić = Никола Лечић fingerprint : FEF3 66AF C90E EDC3 D878 7CDC 956D F4AB A377 1C9B -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iQCVAwUBR8K7SPzDP9K2CKGYAQPGvwP/RzRuWCrnrI9GVPfuY2XMCNDs/aB+G7Oc PXrtce1dgdVwyc1kBbSGR0DHjZ1AaaM1LOYmkbnBa5rTenM4gpKYKrfpl0UIjiM4 /9C+GzeyTmFzUcNA7S/nfnR4PhFxc9lereBSDjgrl02W71G2BWAJdJ8O6+wRXgD9 c6xACTy4fY8= =40Hb -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- 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]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Not sure why print/lyx15 is marked BROKEN
Erwin Lansing [EMAIL PROTECTED] wrote: On Sat, Feb 02, 2008 at 01:28:14PM -0500, Bill Moran wrote: The above mentioned port is marked BROKEN because it does not build with GCC 4.2 Are you sure you are looking at the right port? Yes. print/lyx15 is marked BROKEN on all platforms and releases, not just for gcc 4.2. My mistake. However, it does not change anything else about my experience. I commented out the BROKEN line, figuring I'd see if I could help fix it, but much to my surprise it built without problems and runs just fine. See one of the error logs: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2008012319/lyx-1.5.3.log Mystery of all mysteries ... $ uname -a FreeBSD monster 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #2: Sun Dec 30 11:59:30 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 $ pkg_info | grep lyx lyx-1.5.3 Document processor interfaced with LaTeX (nearly WYSIWYG) So, what information is useful to solving this? -- 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]
Not sure why print/lyx15 is marked BROKEN
The above mentioned port is marked BROKEN because it does not build with GCC 4.2 I commented out the BROKEN line, figuring I'd see if I could help fix it, but much to my surprise it built without problems and runs just fine. $ gcc -v Using built-in specs. Target: i386-undermydesk-freebsd Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 4.2.1 20070719 [FreeBSD] $ uname -a FreeBSD monster 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #2: Sun Dec 30 11:59:30 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Perhaps someone else could verify this, and the port could be unBROKENed? -Bill ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsd.php.mk suggestion
In response to Dominic Fandrey [EMAIL PROTECTED]: Vladimir Zorin wrote: I tried to get in touch with Alex Dupre, the maintainer of the bsd.php.mk, sent him the same text as the above with the patch, but I didn't get any response. As far as I know there are several people who tried to contact him regarding the same issue but, alas, didn't get any response as well. I suppose there might be the possibility of a timeout that allows committing without Maintainer feedback, if you submit it as a PR. This is exactly the way to proceed. If the maintainer is not responding, open the issue as a PR so it's officially tracked. If the maintainer does not respond withing a reasonable length of time, request a maintainer timeout to have another committer check in the patch. -- 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: bsd.php.mk suggestion
In response to Vladimir Zorin [EMAIL PROTECTED]: Bill Moran wrote: In response to Dominic Fandrey [EMAIL PROTECTED]: Vladimir Zorin wrote: I tried to get in touch with Alex Dupre, the maintainer of the bsd.php.mk, sent him the same text as the above with the patch, but I didn't get any response. As far as I know there are several people who tried to contact him regarding the same issue but, alas, didn't get any response as well. I suppose there might be the possibility of a timeout that allows committing without Maintainer feedback, if you submit it as a PR. This is exactly the way to proceed. If the maintainer is not responding, open the issue as a PR so it's officially tracked. If the maintainer does not respond withing a reasonable length of time, request a maintainer timeout to have another committer check in the patch. Thank you for the tip, I'll do the way you described. What regards reasonable length of time - a fortnight, for example, is reasonable enough? There is an actual documented policy on this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-maintainer.html -- 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]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
In response to Tuomo Valkonen [EMAIL PROTECTED]: On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote: On Thu, Dec 13, 2007 at 08:30:06AM +, Tuomo Valkonen wrote: The copyright holder reserves the right to refine the definition of significant changes on a per-case basis. In other words, a moving target -- which implies, to me, that to be legally in the clear, that we would first have to vet every possible change or modification, including patches. Notice the a priori: it means you're allowed to do that without legal threat until further notice to the contrary. Did you not understand the part where Mark described the requirement to avoid possible legal trouble? Since you felt the need to snip out the part of Mark's post that was truly relevant to your reply, I'll reproduce it here: But in the case of implied threat of legal action, in my opinion, it's not worth anyone's time to try to iterate over every possibility to find out to make sure they -- and others, on their behalf -- aren't somehow liable. The risk is simply too high. Stop abusing this mailing list for your own purposes. Let's state some facts: *) FreeBSD has agreed to remove the offending port in order to comply with your license requirements. However, you continue to complain. *) _Anyone_ could submit a patch to the port to abide by your license requirements and it's likely that it will be committed, yet _nobody_ has. Even you, Tuomo, claim to have bold and revolutionary ideas on package distribution yet would rather argue than WRITE A PATCH AND SUBMIT IT! Beyond that, you've _IGNORED_ posts that I've made in the past suggesting this. *) You blame distro folks as abusing developers and expecting them to just provide free work, then you turn around an complain that the FreeBSD people should bend over backwards to accommodate the software you wrote. You're doing the _exact_ thing you accuse others of doing. *) You continually abuse this mailing list by twisting other persons posts to your agenda by snipping relevant information, replying only to the parts that you want to, and redirecting the meaning of other posts. Please go somewhere that you can find emotional healing Tuomo. I, for one, will be glad to see you return as a sane person but have no desire to watch this thread continue as long as you're sick. -- 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: Ion3 removal (Re: Ion3 license violation)]
In response to Mikhail Teterin [EMAIL PROTECTED]: On четвер 13 грудень 2007, Peter Jeremy wrote: = So far one person has stated that they tried and gave = up. Maybe the next person will be more successful. Absolutely right. My point, however, was that the rashed removal makes that hypothetical next person's job more difficult. There was nothing rash about it. Any lawyer will tell you that under the threat of legal action, you remove the threat, _then_ look in to creative ways to fix the problem. There was not an immediate answer to hand. As a result, Mark did the right thing and protected the FreeBSD project from any potential legal action until a better solution can be found. Any claims of license violations -- which, according to Mark, lead to the hasty removal -- should've been addressed by using FORBIDDEN/IGNORE instead. Perhaps you're right. However, I'd like to hear the opinion of a lawyer as to whether this is acceptable or not. -- 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: Ion3 removal (Re: Ion3 license violation)
In response to [EMAIL PROTECTED] (Mark Linimon): On Thu, Dec 13, 2007 at 02:43:07PM +, Tuomo Valkonen wrote: And at least where I come from, contracts are legally enforceable, even if they're only oral ones You clearly don't come from the US, where oral contracts are not germane in business law. What's written down in the license is the only thing that would be germane in court. Again, I'm not a lawyer, but this was my clear understanding from the courses I took. As a side note ... when I owned part of a business we had to got to court with a few clients over gross misunderstandings. As a result, I had a lawyer tell me exactly what you said: That verbal agreements _are_ legally binding, but almost never enforceable. As a result, they're not really germane to business law. At one point, a judge took me aside an told me to start making my clients sign agreements before doing any work, otherwise I was going to end up in serious trouble at some point. It's the reason why, in the US, agreeing to anything over the phone is a bad idea. Ever have a pushy salesman on the phone try to get you to agree to something _right_away_! They reason they do that is it's pretty much impossible to make them liable for misrepresentation or anything like that if you don't have it in writing. They can basically lie through their teeth and promise you the world without delivering, and it's damn near impossible to take legal action against them if it was all verbal. Of course, I am not a lawyer either, so you should consult with one before entering into any important agreement. -- 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: Ion3 license violation
In response to Tuomo Valkonen [EMAIL PROTECTED]: On 2007-12-12, Mark Linimon [EMAIL PROTECTED] wrote: No, the release packages were already built. You see, part of the problem of software Quality Assurance is that it takes some Distro Quality Assurance... ROTFLMAO. If we're taking a vote, I vote for the following: a) We ban Tuomo from our lists. b) We remove all his software from the ports and refuse to accept any more by him. The guy is obviously just around to start flame wars. -- 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: Ion3 license violation
In response to Russell Jackson [EMAIL PROTECTED]: Russell Jackson wrote: Damn it. I use this software, and I even feel somewhat responsible for perhaps possibly Tuomo here after I reported a crash under FreeBSD 7 on the ion list that wound up having something to do with the mod_xinerama extension -- something that I haven't had time to further look into. The simple fact is that Tuomo has some strange desire to blame packagers for all his problems with software and users. It's impossible for the FreeBSD ports system to guarantee compliance with his arbitrarily chosen 28 days rule. If he's going to demand that his terms be followed, then it has to come out of the ports. -- 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: Ion3 license violation
In response to Tuomo Valkonen [EMAIL PROTECTED]: On 2007-12-12, Russell Jackson [EMAIL PROTECTED] wrote: Damn it. I use this software, and I even feel somewhat responsible Don't worry, you're not responsible (much). I'd been monitoring the situation having heard of a ports freeze, and nothing having been done to mark the Ion package as (potentially) obsolete or anything. Not much asked, but it seems distros don't like to admit that they distribute obsolete and buggy software. Translation: Tuomo was just waiting around in the hopes that he could start bitching and cause trouble. He could have pre-emptivly offered his assistance to ensure that the FreeBSD ports tree didn't drift too far out of sync, but instead he just waited around until the opportune moment to start bitching and crying like a baby. If you were watching, why didn't you point this out back at the beginning of the ports freeze? I wasn't running the version in ports CVS. I was running a modified local port that did pull the latest ion sources. I also had to explicitly enable mod_xinerama with a make define; so, it isn't part of the the binary package or a default port install. The option doesn't seem Ion-specific and isn't documented to add unsupported features. A much better place for the module would in any case be, say, x11-wm/ion-3-extras/mod_shit-o-rama. You could also have mod_xrandr, mod_ionflux, and etc. under that kind of setup. There's no reason why the module should deceivingly (and inconveniently) be distributed hidden within the ion-3 package. Either you didn't understand Russell's comment, or you're so bent on blaming folks problems on distro folks that you're redirecting the conversation in an attempt to prove your point, whatever it is. I really don't see why the extreme action of removing it from ports was necessary. :sigh: Distro folks are not reasonable; they think authors should be their undemanding and unquestioning slaves. I think we have learned that already. Who's we? You and all the voices in your head? Remind the voices that FreeBSD isn't a Linux distro, and maybe they'll start feeding you accurate information instead of making you look insane. -- 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: Ion3 license violation
In response to Tuomo Valkonen [EMAIL PROTECTED]: On 2007-12-12, Bill Moran [EMAIL PROTECTED] wrote: It's impossible for the FreeBSD ports system to guarantee compliance with his arbitrarily chosen 28 days rule. There is no 28 days rule. There is a latest release in 28 days or prominently mark (potentially) obsolete rule. You can make the marking permanent, always requiring users to acknowledge a message. You can make the marking automatic, by checking the website for a new release (as Debian presently does), or by some more sophisticated means or dead man triggers. There you go. I had no idea it would be this easy. Please open a PR and attach a patch. -- 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: Ion3 removal (Re: Ion3 license violation)
Mikhail Teterin [EMAIL PROTECTED] wrote: The simple fact is that Tuomo has some strange desire to blame packagers for all his problems with software and users. Yes, license-crafting lawyers are usually more polite and don't engage in direct communications with forums such as ours. Their licenses suck much more, however -- think Java, cdrtools, or Skype, and all the other closed-source packages. Put Tuomo's demands in perspective, for crying out loud... What perspective? The port does not meet his license requirements. Nobody has submitted patches to make it meet said requirements. The project has to remove it. What perspective do I have to keep? Oh, you mean the part where he comes onto the FreeBSD lists and insults all the hard-working ports maintainers? Sure, I'll keep that in perspective. It's impossible for the FreeBSD ports system to guarantee compliance with his arbitrarily chosen 28 days rule. If he's going to demand that his terms be followed, then it has to come out of the ports. Actually, it can be done -- when building the port, the date on the distfile (or that on the most recent source-file /extracted/ therefrom) can be checked against the current date and a prominent message can be issued warning of possible obsoleteness (sp?)... Sure. As I already stated: please submit a patch. Without someone who actually cares enough to patch the port, it must be removed do to license problems. This is _no_ different than any other port with similar conflicts between licensing and available manpower to meet those licensing requirements. The _only_ difference is that Tuomo thought it necessary to come onto our lists and make a big stink about it, filling my inbox to overflowing. I just wish we avoided the rash decisions like let's remove everything written by the guy we don't like NOW -- if only in the name of ports slush... In the hurry to spite the admittedly unpleasant-sounding author, the needs and expectations of the users were neglected. Well, I said that because the guy irritates me. Let me be clear on this point. I maintain a few ports. I am _NOT_ in a position to dictate policy, I was only stating my opinion -- which _MUST_ not be construed to be the overall opinion of the FreeBSD community. There are far too many quality hackers out there who _do_ care about the community to tolerate one who seems to be in conflict with his community. I've never used ion, but, judging from some responses here, it is an appreciated piece of software. Fair enough. In that case, those who appreciate it should submit patches that meet Tuomo's requirements. This is how it's done. This is how it's _always_ been done. If the original maintainer is no longer keeping up with the software, then someone else needs to step up. It's his software. If his requirements can't be met, then the port comes out of the tree. What else do you expect to happen? -- 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: Ion3 removal (Re: Ion3 license violation)
Mikhail Teterin [EMAIL PROTECTED] wrote: середа 12 грудень 2007 06:35 по, Bill Moran Ви написали: It's his software. If his requirements can't be met, then the port comes out of the tree. What else do you expect to happen? I expect the port-removal to be initiated/done in an orderly fashion. This includes marking it FORBIDDEN (or IGNORE, or BROKEN): FORBIDDEN= Violates licensing requirements of the author and: EXPIRATION_DATE=Some date a few months from now This would give those people, whom you expect to submit patches, some time to, actually, create them... Only if nothing materializes by the expiration date, should the port be deleted. It's absolutely a shame that couldn't be done, but he demanded that the port be fixed prior to release. Without a fix to hand, the only way to guarantee that FreeBSD wouldn't be in violation of the license agreement was to pull the port. Generate a patch and submit it. I'm sure the port will be reinstated as soon as somebody does so. -- 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]
