[HEADSUP] new portmgr recommendation about adding new ports
Here is the result of a discussion amongst the portmgr members during the past few weeks, in response to the large number of new ports added to the Ports Collection in the last few months. - Recently we've seen evidence of an increase in the number of ports that are submitted just because the software is there, and not out of any underlying need for the port to exist. When considering a new port, portmgr would like to ask you to please apply the following criterion: New ports should only be submitted by someone who is actually using the software and will continue to use the port to maintain the software. Adding a port of software that you do not personally use, or do not use within the FreeBSD ports collection (such as an xpi browser extension that you manage using firefox and not using the Ports Collection), is not a good tradeoff between adding functionality and adding complexity. Each additional port requires resources, both machine (from the package building system) and people (to inspect the results from the package building system). This is especially true when you consider that we, as a team, are all trying to keep ports buildable on on 4 different branches and 5 different architectures (with increasing interest in arm and powerpc). Past experience shows that these ports often quickly fall behind as new versions are released, and when build breakages occur, they do not get fixed. In some other cases, some of our contributors try to keep ports viable by fixes and updating long after their real usefulness has passed, and that time could be better spent on the more worthwhile ports. While no one is suggesting that we go the route some projects have with some kind of 'gateway' process for approving new ports, at some point the number of ports will simply be too great for our infrastructure (package building system, sending PRs via email). Some common sense should help to keep us from reaching that point. As a reminder, the Ports Collection already has 198 ports marked BROKEN*, and 4291 unmaintained ones. We really don't need to add to these numbers. To summarize, we simply can't support all the possible applications out on the Internet, so we need to use common sense to try to keep it down to a maintainable number. mcl (*: on i386-6; the numbers are higher on the other architectures, and -CURRENT) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: pound-1.9
Dear Anders I'm about to test pound on one of my freeBSD machines and saw that the version of the port is 1.9. Is there any plans on updating the port to 2.1.2? Cheers Mattias ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade and starting servers after upgrade.
* Peter Jeremy [EMAIL PROTECTED] [2006-09-19]: On Tue, 2006-Sep-19 07:04:56 +0200, Martin Nilsson wrote: For instance every time I portupgrade dhcpd I have to remember to start it manually after the upgrade. As portupgrade knows how to stop the daemon before the upgrade it should also know how to start it afterwards. Stopping the daemon is easy: /usr/local/etc/rc.d/ stop. Starting it afterwards is not quite as easy because, portupgrade should restore the state of the daemon to the state prior to it starting, not just start it automatically. (The administrator may have manually stopped the daemon). Good point, but isn't it as easy to check the status before stopping it: /usr/local/etc/rc.d/ status? You could even check the reported pid. If the status is in some way unclear to portupgrade, portupgrade could warn the user - Service X not started again - unknown status. Or am I doing it too easy? Hans ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade and starting servers after upgrade.
On Tue, Sep 19, 2006 at 05:46:00PM +1000 I heard the voice of Peter Jeremy, and lo! it spake thus: Stopping the daemon is easy: /usr/local/etc/rc.d/ stop. More to the point, portupgrade doesn't stop it. pkg_delete does, because stopping it is in the plist. e.g., for spamassassin: % grep sa-spamd /var/db/pkg/p5-Mail-SpamAssassin-3.1.5/+CONTENTS | grep stop @unexec %D/etc/rc.d/sa-spamd.sh stop /dev/null 21 || true @unexec %D/etc/rc.d/sa-spamd stop /dev/null 21 || true -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade and starting servers after upgrade.
On 9/19/06, Hans F. Nordhaug [EMAIL PROTECTED] wrote: Good point, but isn't it as easy to check the status before stopping it: /usr/local/etc/rc.d/ status? You could even check the reported pid. If the status is in some way unclear to portupgrade, portupgrade could warn the user - Service X not started again - unknown status. Or am I doing it too easy? Especially since daemon configuration changes from time to time, you can't necessarily restart a daemon at all after an upgrade. Dave. -- Strange women lying in ponds distributing swords is no basis for a system of government. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade and starting servers after upgrade.
Is there a policy about how to deal with running daemons and portupgrade? For instance every time I portupgrade dhcpd I have to remember to start it manually after the upgrade. As portupgrade knows how to stop the daemon before the upgrade it should also know how to start it afterwards. Read /usr/local/etc/pkgtools.conf, specifically the 'AFTERINSTALL' part... eg. 'databases/mysql*server' = '/usr/local/etc/rc.d/mysql-server restart', /Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QT related issue (ports/102829)
Vasil Dimov wrote: Hi, Can someone familiar with the QT tools uic and moc take a look at ports/102829 - the port in question is using scons and the directory /usr/X11R6/etc/settings/ is being created during build but probably the problem is not in the port or the software itself but rather in qt or scons. It looks very mysterious to me. Any help is appreciated, thanks in advance! http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/92532 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: QT related issue (ports/102829)
On Tue, Sep 19, 2006 at 08:57:15PM +1000, Sam Lawrance wrote:
Vasil Dimov wrote:
Hi,
Can someone familiar with the QT tools uic and moc take a look at
ports/102829 - the port in question is using scons and the directory
/usr/X11R6/etc/settings/ is being created during build but probably
the problem is not in the port or the software itself but rather in
qt or scons. It looks very mysterious to me.
Any help is appreciated, thanks in advance!
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/92532
Even if I do ``make PACKAGE_BUILDING=y'' the directory
/usr/X11R6/etc/settings gets created (during build).
What is the idea of this code:
.if defined(PACKAGE_BUILDING)
TMPDIR?=/tmp
MAKE_ENV+= TMPDIR=${TMPDIR}
CONFIGURE_ENV+= TMPDIR=${TMPDIR}
.endif
in bsd.kde.mk? (the port has USE_QT_VER=3)
--
Vasil Dimov
[EMAIL PROTECTED]
%
A complex system designed from scratch never works and
cannot be patched up to make it work. You have to start
over, beginning with a working simple system.
pgpjnMCMhWTe6.pgp
Description: PGP signature
[Fwd: log4cxx-devel aka log4cxx-0.9.8 suggestion]
If there is anybody actively using log4cxx and having time/resources to do some port work for it, you might be interested in the forwarded message. As I described below, I did manual compilation once for one time job, unfortunately I don't have resources now to do a proper port (and I will not need to use log4cxx again in the nearest time). Unfortunately, Thaddeus Covert, the maintainer of the port, hasn't replied yet. Original Message Subject: log4cxx-devel aka log4cxx-0.9.8 suggestion Date: Fri, 01 Sep 2006 14:41:15 +0300 From: Andriy Gapon [EMAIL PROTECTED] To: Thaddeus Covert [EMAIL PROTECTED] Thaddeus, in view of the following message on log4cxx page and real development needs: http://logging.apache.org/log4cxx/ At this point, log4cxx-0.9.7 is substantially out of date, has known serious deficiencies that have been resolved in the CVS, and should be avoided for new code. I would like to suggest to create log4cxx-devel port, so that we don't have to wait until 0.9.8 is officially released. I was able to compile 0.9.8 based on the current 0.9.7 [port] but with a lot of manual tweaking. So, I would like to share my experience with you: 1. pre-0.9.8 (nightly) sources can be obtained from here: http://littletux.homelinux.org/log4cxx/log4cxx-0.9.8.tar.gz 2. patch file patch-include-log4cxx-helpers-tchar.h is obsolete (as tchar.h) 3. 0.9.8 autoconf process requires some m4 files from apr and apr-utils (port devel/apr) for symbols APR_FIND_APR and APR_FIND_APU. Currently apr port does not install any m4 files in aclocal directory, so I had to manually copy all m4 files (maybe an overkill) from apr build directory into /usr/local/share/aclocal. 4. configure went well after that, but there was one problem with auto-made Makefiles - apr_builddir variable was not set. That variable is used to find libtool: LIBTOOL = $(SHELL) $(apr_builddir)/libtool I am not sure what a correct value of that variable should be, but I manually patched all the Makefiles to add the following line: apr_builddir=$(top_srcdir) This allowed build to proceed using libtool script that comes with log4cxx sources. 5. after that was one build (or rather linking) problem related to src/unicodehelper.cpp file - some functions, that are referenced elsewhere, are only compiled if either _WIN32 or __STDC_ISO_10646__ macro is defined. I am not sure what the latter macro actually means but I added it to DEFS variable in the src/Makefile to amke build happy. I see that some other ports also fiddle with that macro like follows: CONFIGURE_ENV+= CPPFLAGS=... -D__STDC_ISO_10646__ ... 6. after that port compiled and installed, but I never checked things like plist. 7. run-time behavior seems to be ok after testing with a certain application known to heavily use CVS version of log4cxx on Linux. -- Andriy Gapon -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
samba-3.0.23c,1 with winbindd on freebsd 6.1
Timur, please take a look at the following bug report: https://bugzilla.samba.org/show_bug.cgi?id=4109 It might be better to start reading with the first followup and then proceed to original submission. I submitted this bug to Samba as I think it is better to fix their code, but it might turn out that the problem is more specific to FreeBSD libc and there is no problem with Linux glibc. In this case there perhaps might be some reluctance from Samba guys to fix the problem and we might need a port patch. BTW, port patch would be nice anyway until we get samba sources fixed. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: editors/scite port broken
[EMAIL PROTECTED] wrote: On Mon, 18 Sep 2006 10:32:40 -0400, Kris Kennaway wrote On Mon, Sep 18, 2006 at 10:48:52AM +0200, [EMAIL PROTECTED] wrote: : undefined reference to `lua_createtable' LuaExtension.o(.text+0x34d): In function `cf_scite_constname(lua_State*)': [...] The question is why is it trying to use lua when no lua library is being linked (nor is it apparently even present on your system. Unfortunately it is unmaintained IIRW since sobomax stepped down. I used to use the port a lot and submit update PR's, but my knowledge is too limited in regards to C++ et consortes. It happened to me too. The problem is that lua port has been upgraded to 5.1 in the past few months, but scite (as is now) can only be linked to 5.0. I solved it with: portupgrade -fo lang/lua50 lua or equivalent (i.e. uninstall lang/lua and install lang/lua50) Hope this helps Angelo. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade: odd behaviour with -p
Since the recent upgrades (in the last couple of months, I'd say) when I run some variant of: portupgrade -aRp I noticed that, in case some port fails during build or install, the -p option will repackage the existing port. You can verify it by simply pressing ^C during compile phase. I don't think this is the intended behaviour. Angelo Turetta Modena - Italy ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
devel/ace port: thread flags issue
If anybody is actively using ACE on freebsd and has time/resources to do some port work, you might be interested. There is an issue with using ACE default thread flags on FreeBSD with libpthread, the issue is described and discussed in the following message thread: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=5728+0+archive/2006/freebsd-threads/20060903.freebsd-threads Unfortunately, neither ACE people nor ACE port maintainer participated in the conversation, so the problem is still there. My favorite solution would be to go with Daniel Eischen's suggestion and to make THR_NEW_LWP an alias for THR_SCOPE_PROCESS when ACE is built on FreeBSD. This could be done either via port patch or via OS-specific defines of ACE code itself. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: devel/ace port: thread flags issue
on 19/09/2006 18:10 Andriy Gapon said the following: My favorite solution would be to go with Daniel Eischen's suggestion and to make THR_NEW_LWP an alias for THR_SCOPE_PROCESS when ACE is built on ^ I meant to write THR_SCOPE_SYSTEM here FreeBSD. This could be done either via port patch or via OS-specific defines of ACE code itself. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: ipmi-kmod-20060418_1
Michael Graziano writes: | I believe our 2950 is BIOS Rev. A03 as well, I'll reboot it tomorrow | if I have a chance and get the Dell version ID. | | dmesg-wise, my first iomem range is the same as for A02, but my | second is not. I'm leaning toward the explanation that Dell moved | something on us and done went and broke the module :-/ | | ipmi0: System Management BIOS at iomem 0xfd040-0xfd05e, | 0xcffbc000-0xcffbcc3a on isa0 | ipmi0: SMBIOS Version: 2.04, revision: 2.04 | ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa | ipmi0: couldn't configure smbios io res FYI, this will be fixed in -current soon. jhb has been doing some work in the area to greatly improve some WIP that I gave him. Dell put a hole in the address range via their ACPI so it can't attach the range. Doug A. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: editors/scite port broken
On Tue, 19 Sep 2006 15:25:46 +0200, Angelo Turetta wrote [EMAIL PROTECTED] wrote: On Mon, 18 Sep 2006 10:32:40 -0400, Kris Kennaway wrote On Mon, Sep 18, 2006 at 10:48:52AM +0200, [EMAIL PROTECTED] wrote: : undefined reference to `lua_createtable' LuaExtension.o(.text+0x34d): In function `cf_scite_constname(lua_State*)': [...] The question is why is it trying to use lua when no lua library is being linked (nor is it apparently even present on your system. Unfortunately it is unmaintained IIRW since sobomax stepped down. I used to use the port a lot and submit update PR's, but my knowledge is too limited in regards to C++ et consortes. It happened to me too. The problem is that lua port has been upgraded to 5.1 in the past few months, but scite (as is now) can only be linked to 5.0. I solved it with: portupgrade -fo lang/lua50 lua or equivalent (i.e. uninstall lang/lua and install lang/lua50) It solves the problem. Thanks a lot. Maybe then we should check in the port whether wrong version of lang/lua is installed, and if so mark it IGNORE. Or maybe CONFLICT is in place, but it is not really a conflict rather ports incompatibility. -- Piotr Smyrak [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to Contact MPICH Team?
Le Mar 19 sep 06 à 16:47:50 +0200, Intron is my alias on the Internet [EMAIL PROTECTED] écrivait : Hi, Hello, I'd like to submit my patches for MPICH 2 to the developper team. But I haven't got any reply from them after I sent mail to [EMAIL PROTECTED] . Can you tell me how to contact them indeed? This is the right address - perhaps your mail has been catched by a anti-spam. Besides this address, there is a mailing list: It is called [EMAIL PROTECTED]. Only members of the list can post, but anyone can join. To join this discussion list, send a mail to [EMAIL PROTECTED] containing the line: subscribe mpich-discuss If you have problem with this list, you can send me your patches, and I'll forward them for you. Regards, -- Th. Thomas. pgpfRM82vctjc.pgp Description: PGP signature
Re: [kde-freebsd] Re: QT related issue (ports/102829)
Vasil Dimov schrieb:
On Tue, Sep 19, 2006 at 08:57:15PM +1000, Sam Lawrance wrote:
Vasil Dimov wrote:
Hi,
Can someone familiar with the QT tools uic and moc take a look at
ports/102829 - the port in question is using scons and the directory
/usr/X11R6/etc/settings/ is being created during build but probably
the problem is not in the port or the software itself but rather in
qt or scons. It looks very mysterious to me.
Any help is appreciated, thanks in advance!
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/92532
Even if I do ``make PACKAGE_BUILDING=y'' the directory
/usr/X11R6/etc/settings gets created (during build).
What is the idea of this code:
.if defined(PACKAGE_BUILDING)
TMPDIR?=/tmp
MAKE_ENV+= TMPDIR=${TMPDIR}
CONFIGURE_ENV+= TMPDIR=${TMPDIR}
.endif
in bsd.kde.mk? (the port has USE_QT_VER=3)
You will need to make sure that the TMPDIR environment variable is set
during build (so uic will see it). Scons by default does *not* preserve
and propagate the shell environment it's being called from, so you will
have to modify the main sconscript file to at least import TMPDIR from
the external environment ( see
http://www.scons.org/doc/HTML/scons-user/c1171.html ).
Once you do that, uic will create the temporary configurations files /
directories in TMPDIR (if PACKAGE_BUILDING is set), which is ok'd by
kris and won't flag errors on pointyhat.
Cheers,
--
,_, | Michael Nottebrock | [EMAIL PROTECTED]
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
signature.asc
Description: OpenPGP digital signature
Re: www/dotproject out of date and vulnerable
Hi Fred, thanks for your work on this port. Could you please resubmit the update as a unified diff and send it as a problem report (PR). Otherwise your work will probably get lost in the vast amount of email that gets posted on freebsd-ports. More information in the Porter's Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ Very brief summary: cp -R portdir portdir.orig edit files in portdir diff -ruN portdir.orig portdir port.patch send-pr -a port.patch -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgp5w1T2UlIWD.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
--- Simon Barner [EMAIL PROTECTED] wrote: Hi Fred, thanks for your work on this port. Could you please resubmit the update as a unified diff and send it as a problem report (PR). I'm on my way towards doing that, but I want to get it right beforehand. I want to be able to require MySQL 3.23. That requirement doesn't seem to work because of the indirect dependency through php4-mysql. I'm looking for clues on how to get this to work. Thanks, Fred Otherwise your work will probably get lost in the vast amount of email that gets posted on freebsd-ports. More information in the Porter's Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ Very brief summary: cp -R portdir portdir.orig edit files in portdir diff -ruN portdir.orig portdir port.patch send-pr -a port.patch -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 12:23:55PM -0700, Fred Cox wrote: This is the first time I've tried to modify a port, and I'm having a bit of trouble because this port requires MySQL 3.23 and PHP 4. Those dependencies weren't specified in the port before. I've gotten PHP4 by adding: USE_PHP=gd mysql session DEFAULT_PHP_VER=4 WANT_PHP_WEB= yes IGNORE_WITH_PHP=5 Trying to get it to install MySQL 3.23 client seems to be stymied by the php4-mysql default dependency on the MySQL 5 client. I haven't actually figured out how it specifies this dependency, since the php4-mysql/Makefile is very empty. Basically if php4-mysql wants mysql5 then there is no way around it for your port. You will need to create a php4-mysql3 port that specifies the mysql 3 dependency and use that instead. Is it really a requirement to use this old version of mysql? Kris pgpC63vMyZY4C.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
For my second iteration of installing this through the original port, I was able to install mysql323-client and php4 before installing dotproject, and everything worked. So it appears that php4-mysql will use mysql323-client if it's already installed. I haven't dug through the code to see how that is done, though. There are patches out there for making things work with MySQL 4 and 5. However, they are not officially supported. I am debating putting the patches in for MySQL 5, but if someone goes to the trouble of installing MySQL 3.23 before installing php4-mysql and dotproject, I think it will break. Is there any way of getting the dotproject dependency on MySQL 3.23 to be stronger than the php4-mysql default dependency on mysql5-client? Thanks, Fred --- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 12:23:55PM -0700, Fred Cox wrote: This is the first time I've tried to modify a port, and I'm having a bit of trouble because this port requires MySQL 3.23 and PHP 4. Those dependencies weren't specified in the port before. I've gotten PHP4 by adding: USE_PHP=gd mysql session DEFAULT_PHP_VER=4 WANT_PHP_WEB= yes IGNORE_WITH_PHP=5 Trying to get it to install MySQL 3.23 client seems to be stymied by the php4-mysql default dependency on the MySQL 5 client. I haven't actually figured out how it specifies this dependency, since the php4-mysql/Makefile is very empty. Basically if php4-mysql wants mysql5 then there is no way around it for your port. You will need to create a php4-mysql3 port that specifies the mysql 3 dependency and use that instead. Is it really a requirement to use this old version of mysql? Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
Would you recommend doing the partial job of updating the port for the vulnerability and requiring PHP4 while I work on the ultimate solution? Thanks, Fred --- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 02:15:53PM -0700, Fred Cox wrote: For my second iteration of installing this through the original port, I was able to install mysql323-client and php4 before installing dotproject, and everything worked. So it appears that php4-mysql will use mysql323-client if it's already installed. I haven't dug through the code to see how that is done, though. Yep, you can't rely on that though of course. If the user already has the php4-mysql port installed, or installs it from a package, it will use the default settings. The only solution is what I previously said. Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 02:42:37PM -0700, Fred Cox wrote: Would you recommend doing the partial job of updating the port for the vulnerability and requiring PHP4 while I work on the ultimate solution? It will result in a broken port unless you can address the mysql thing - there's no way around it. Kris pgpPbyw4HbhMZ.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 03:18:01PM -0700, Fred Cox wrote: It's current state is that it will install a vulnerable version with either the installed php and mysql client or php5 and mysql5. In the latter case, there are many bugs in the installed port. If I submit what I have now, it will install the updated version with PHP4. The user will still have to track down the mysql problem until I can do the right thing, but there will be a period of time while I learn about making a port from scratch. I'm trying to get a read on whether imperfect improvement is worth checking in, or whether the typical thing is to wait for perfection, even if that might take a while. Will fail to package is pretty far from perfection in my book :) Mark the port FORBIDDEN if you have to, but a port that will not build with default settings should not be committed. Kris pgpdM7yyQyNdl.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote: Will fail to package is pretty far from perfection in my book :) I don't believe I ever said that. It builds fine and even runs, it just has lots of bugs. Can you let me know what I said that gave you that impression? Fred Mark the port FORBIDDEN if you have to, but a port that will not build with default settings should not be committed. Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 03:25:45PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: Will fail to package is pretty far from perfection in my book :) I don't believe I ever said that. It builds fine and even runs, it just has lots of bugs. Can you let me know what I said that gave you that impression? Based on what we've discussed, the proposed changes to the port will make it fail to build with default settings (since mysql 4 will be installed), for example on the package build cluster. Kris pgpdybh2PSuKh.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 03:25:45PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: Will fail to package is pretty far from perfection in my book :) I don't believe I ever said that. It builds fine and even runs, it just has lots of bugs. Can you let me know what I said that gave you that impression? Based on what we've discussed, the proposed changes to the port will make it fail to build with default settings (since mysql 4 will be installed), for example on the package build cluster. I missed that requirement. So basically, until it can run with PHP 5 and MySQL 5, it's not good enough to be a port. Restricting it to run with PHP 4 will mean that it will be rejected? Fred Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 04:00:14PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 03:25:45PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: Will fail to package is pretty far from perfection in my book :) I don't believe I ever said that. It builds fine and even runs, it just has lots of bugs. Can you let me know what I said that gave you that impression? Based on what we've discussed, the proposed changes to the port will make it fail to build with default settings (since mysql 4 will be installed), for example on the package build cluster. I missed that requirement. So basically, until it can run with PHP 5 and MySQL 5, it's not good enough to be a port. Restricting it to run with PHP 4 will mean that it will be rejected? No, I guess you've still misunderstood. I don't know how many times I can say this, but let me try to explain once more: your port should be buildable with the default settings of all ports involved. This means that you can't place special requirements like you have to first install mysql 3.x, then install the php4-mysql port, then install this port, because that is too non-generic and will not be true on systems that already have php4-mysql installed with the default mysql client. The solution, which I explained several messages ago, is to make an alternative php4-mysql3 port, which always depends on mysql 3.x, and use that instead of php4-mysql (it may need to conflict with php4-mysql, I don't know). This really isn't very hard and you perhaps could have done it already by now :) Kris pgp0eXfQcpW2J.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 04:00:14PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 03:25:45PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: Will fail to package is pretty far from perfection in my book :) I don't believe I ever said that. It builds fine and even runs, it just has lots of bugs. Can you let me know what I said that gave you that impression? Based on what we've discussed, the proposed changes to the port will make it fail to build with default settings (since mysql 4 will be installed), for example on the package build cluster. I missed that requirement. So basically, until it can run with PHP 5 and MySQL 5, it's not good enough to be a port. Restricting it to run with PHP 4 will mean that it will be rejected? No, I guess you've still misunderstood. I don't know how many times I can say this, but let me try to explain once more: your port should be buildable with the default settings of all ports involved. This means that you can't place special requirements like you have to first install mysql 3.x, then install the php4-mysql port, then install this port, because that is too non-generic and will not be true on systems that already have php4-mysql installed with the default mysql client. The solution, which I explained several messages ago, is to make an alternative php4-mysql3 port, which always depends on mysql 3.x, and use that instead of php4-mysql (it may need to conflict with php4-mysql, I don't know). This really isn't very hard and you perhaps could have done it already by now :) When I was trying to install this in first place, I couldn't install mysql323-client when mysql5-client was already installed. It refused to install. I had to install it into a jail by itself with msyql323 and php4. I assume that will break the requirement that it be buildable with defaults, assuming that some other port that requires mysql has already been built. Is that a bad assumption? Thanks for the education, Fred Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 04:19:23PM -0700, Fred Cox wrote: No, I guess you've still misunderstood. I don't know how many times I can say this, but let me try to explain once more: your port should be buildable with the default settings of all ports involved. This means that you can't place special requirements like you have to first install mysql 3.x, then install the php4-mysql port, then install this port, because that is too non-generic and will not be true on systems that already have php4-mysql installed with the default mysql client. The solution, which I explained several messages ago, is to make an alternative php4-mysql3 port, which always depends on mysql 3.x, and use that instead of php4-mysql (it may need to conflict with php4-mysql, I don't know). This really isn't very hard and you perhaps could have done it already by now :) When I was trying to install this in first place, I couldn't install mysql323-client when mysql5-client was already installed. It refused to install. I had to install it into a jail by itself with msyql323 and php4. Right, they conflict. There's nothing you can do about that; they want to install files on top of each other, breaking one or the other installation. I assume that will break the requirement that it be buildable with defaults, assuming that some other port that requires mysql has already been built. Is that a bad assumption? Yes, with the above solution mysql 4.x or 5.x do not get installed when you build your port on a clean system (no ports installed, and no non-default settings), only mysql 3.x, so there's no conflict. If someone has mysql 4.x or 5.x installed already, they get a warning from the conflict checking telling them it's impossible to install the port without first deinstalling mysql 4.x and 5.x, which is true and unavoidable. With your proposed version, a conflicting mysql version would first be installed by php4-mysql and the build of your port will subsequently fail when it tries to install mysql3 (or vice versa, depending on which happens first), which is precisely the problem. Hope this has clarified things sufficiently now, Kris pgpP7roVakRWY.pgp Description: PGP signature
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 04:19:23PM -0700, Fred Cox wrote: No, I guess you've still misunderstood. I don't know how many times I can say this, but let me try to explain once more: your port should be buildable with the default settings of all ports involved. This means that you can't place special requirements like you have to first install mysql 3.x, then install the php4-mysql port, then install this port, because that is too non-generic and will not be true on systems that already have php4-mysql installed with the default mysql client. The solution, which I explained several messages ago, is to make an alternative php4-mysql3 port, which always depends on mysql 3.x, and use that instead of php4-mysql (it may need to conflict with php4-mysql, I don't know). This really isn't very hard and you perhaps could have done it already by now :) When I was trying to install this in first place, I couldn't install mysql323-client when mysql5-client was already installed. It refused to install. I had to install it into a jail by itself with msyql323 and php4. Right, they conflict. There's nothing you can do about that; they want to install files on top of each other, breaking one or the other installation. I assume that will break the requirement that it be buildable with defaults, assuming that some other port that requires mysql has already been built. Is that a bad assumption? Yes, with the above solution mysql 4.x or 5.x do not get installed when you build your port on a clean system (no ports installed, and no non-default settings), only mysql 3.x, so there's no conflict. If someone has mysql 4.x or 5.x installed already, they get a warning from the conflict checking telling them it's impossible to install the port without first deinstalling mysql 4.x and 5.x, which is true and unavoidable. With your proposed version, a conflicting mysql version would first be installed by php4-mysql and the build of your port will subsequently fail when it tries to install mysql3 (or vice versa, depending on which happens first), which is precisely the problem. Actually, it doesn't. It goes ahead and installs it, even though I specified these: WITH_MYSQL= yes WANT_MYSQL_VER= 323 IGNORE_WITH_MYSQL=5 Starting with a system that had no MySQL or PHP installed on it, I did a make install in the dotproject port with the Makefile and distinfo I specified earlier. It seems to look for mysql.so, and if that's found, it doesn't worry about the version. See the log at http://fcox.net/dp.log, when no mysql or php was installed on the system. Perhaps this is a bug in the dependencies system. Hope this has clarified things sufficiently now, It certainly presents a certain model, but my experience doesn't match up with it. That's why I was confused, Fred Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 05:15:45PM -0700, Fred Cox wrote: Actually, it doesn't. It goes ahead and installs it, even though I specified these: WITH_MYSQL= yes WANT_MYSQL_VER= 323 IGNORE_WITH_MYSQL=5 Starting with a system that had no MySQL or PHP installed on it, I did a make install in the dotproject port with the Makefile and distinfo I specified earlier. It seems to look for mysql.so, and if that's found, it doesn't worry about the version. OK, so it's just silently broken, which is worse. See the log at http://fcox.net/dp.log, when no mysql or php was installed on the system. Perhaps this is a bug in the dependencies system. Dunno without investigating. Anyway, the correct solution is the same. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 05:15:45PM -0700, Fred Cox wrote: Actually, it doesn't. It goes ahead and installs it, even though I specified these: WITH_MYSQL= yes WANT_MYSQL_VER= 323 IGNORE_WITH_MYSQL=5 Starting with a system that had no MySQL or PHP installed on it, I did a make install in the dotproject port with the Makefile and distinfo I specified earlier. It seems to look for mysql.so, and if that's found, it doesn't worry about the version. OK, so it's just silently broken, which is worse. It's still better than the current situation. See the log at http://fcox.net/dp.log, when no mysql or php was installed on the system. Perhaps this is a bug in the dependencies system. Dunno without investigating. Anyway, the correct solution is the same. OK, so if you had a pointer on how to depend on that alternate version, it would help. Right now, the dependencies are specified with the WITH and IGNORE variables, but it seems that with your proposal I won't be able to do that. Maybe tonight I will fall asleep reading the Porter's Handbook. Fred Kris __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 06:02:52PM -0700, Fred Cox wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Sep 19, 2006 at 05:15:45PM -0700, Fred Cox wrote: Actually, it doesn't. It goes ahead and installs it, even though I specified these: WITH_MYSQL= yes WANT_MYSQL_VER= 323 IGNORE_WITH_MYSQL=5 Starting with a system that had no MySQL or PHP installed on it, I did a make install in the dotproject port with the Makefile and distinfo I specified earlier. It seems to look for mysql.so, and if that's found, it doesn't worry about the version. OK, so it's just silently broken, which is worse. It's still better than the current situation. Publishing packages that will not run because they're linked to the wrong libraries is, again, not my idea of better. See the log at http://fcox.net/dp.log, when no mysql or php was installed on the system. Perhaps this is a bug in the dependencies system. Dunno without investigating. Anyway, the correct solution is the same. OK, so if you had a pointer on how to depend on that alternate version, it would help. Copy the php4-mysql port to php4-mysql3 and make the presumably trivial change to make it use mysql 3 instead of whatever the default is. Right now, the dependencies are specified with the WITH and IGNORE variables, but it seems that with your proposal I won't be able to do that. Maybe tonight I will fall asleep reading the Porter's Handbook. OK. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: ipmi-kmod-20060418_1
On Sep 19, 2006, at 10:03 AM, Doug Ambrisko wrote: Michael Graziano writes: | I believe our 2950 is BIOS Rev. A03 as well, I'll reboot it tomorrow | if I have a chance and get the Dell version ID. | | dmesg-wise, my first iomem range is the same as for A02, but my | second is not. I'm leaning toward the explanation that Dell moved | something on us and done went and broke the module :-/ | | ipmi0: System Management BIOS at iomem 0xfd040-0xfd05e, | 0xcffbc000-0xcffbcc3a on isa0 | ipmi0: SMBIOS Version: 2.04, revision: 2.04 | ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa | ipmi0: couldn't configure smbios io res FYI, this will be fixed in -current soon. jhb has been doing some work in the area to greatly improve some WIP that I gave him. Dell put a hole in the address range via their ACPI so it can't attach the range. That's great. I'll keep an eye on the commits to the IPMI code in - current, and can update the sysutils/ipmi-kmod port with a new snapshot when that new code gets in. Nick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Sep 19, 2006 at 06:02:52PM -0700, Fred Cox
wrote:
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Sep 19, 2006 at 05:15:45PM -0700, Fred
Cox
wrote:
Actually, it doesn't. It goes ahead and
installs
it,
even though I specified these:
WITH_MYSQL= yes
WANT_MYSQL_VER= 323
IGNORE_WITH_MYSQL=5
Starting with a system that had no MySQL or
PHP
installed on it, I did a make install in the
dotproject port with the Makefile and distinfo
I
specified earlier.
It seems to look for mysql.so, and if that's
found, it
doesn't worry about the version.
OK, so it's just silently broken, which is
worse.
It's still better than the current situation.
Publishing packages that will not run because
they're linked to the
wrong libraries is, again, not my idea of better.
There is no linkage problem. It's a client/server
problem.
PHP4 is perfectly happy being linked with the MySQL 5
client libraries, it's the database server that needs
to be 3.23. The SQL used in dotProject is legal for
3.23, but not 5.
See the log at http://fcox.net/dp.log, when no
mysql
or php was installed on the system.
Perhaps this is a bug in the dependencies
system.
Dunno without investigating. Anyway, the
correct
solution is the
same.
OK, so if you had a pointer on how to depend on
that
alternate version, it would help.
Copy the php4-mysql port to php4-mysql3 and make the
presumably
trivial change to make it use mysql 3 instead of
whatever the default
is.
It's not trivial. The current Makefile is trivial,
but a change to do what you're suggesting will need to
be more complex.
Here's the current php4-mysql Makefile:
CATEGORIES= databases
MASTERDIR= ${.CURDIR}/../../lang/php4
PKGNAMESUFFIX= -mysql
.include ${MASTERDIR}/Makefile
The ${MASTERDIR}/Makefile doesn't refer to mysql at
all.
Personally, I don't see how it knows it's supposed to
link MySQL in there. Perhaps it's because PHP4
defaults to including MySQL support, so this isn't
really doing anything. I haven't read far enough to
know for sure.
Right now, the
dependencies are specified with the WITH and
IGNORE
variables, but it seems that with your proposal I
won't be able to do that. Maybe tonight I will
fall
asleep reading the Porter's Handbook.
OK.
Kris
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 06:25:50PM -0700, Fred Cox wrote:
It's still better than the current situation.
Publishing packages that will not run because
they're linked to the
wrong libraries is, again, not my idea of better.
There is no linkage problem. It's a client/server
problem.
PHP4 is perfectly happy being linked with the MySQL 5
client libraries, it's the database server that needs
to be 3.23. The SQL used in dotProject is legal for
3.23, but not 5.
Then you haven't explained yourself very well, because at the start of
this thread you were talking about a conflict between the mysql 3 and
mysql 5 *clients*, not servers.
--
Trying to get it to install MySQL 3.23 client seems to
be stymied by the php4-mysql default dependency on the
MySQL 5 client. I haven't actually figured out how it
specifies this dependency, since the
php4-mysql/Makefile is very empty.
--
So, does it or does it not require the mysql 3.23 client in
php4-mysql and dotproject?
Copy the php4-mysql port to php4-mysql3 and make the
presumably
trivial change to make it use mysql 3 instead of
whatever the default
is.
It's not trivial. The current Makefile is trivial,
but a change to do what you're suggesting will need to
be more complex.
Here's the current php4-mysql Makefile:
CATEGORIES= databases
MASTERDIR= ${.CURDIR}/../../lang/php4
PKGNAMESUFFIX= -mysql
.include ${MASTERDIR}/Makefile
The ${MASTERDIR}/Makefile doesn't refer to mysql at
all.
Personally, I don't see how it knows it's supposed to
link MySQL in there. Perhaps it's because PHP4
defaults to including MySQL support, so this isn't
really doing anything. I haven't read far enough to
know for sure.
Look in bsd.php.mk for the rest.
Kris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
--- Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Sep 19, 2006 at 06:25:50PM -0700, Fred Cox
wrote:
It's still better than the current situation.
Publishing packages that will not run because
they're linked to the
wrong libraries is, again, not my idea of
better.
There is no linkage problem. It's a client/server
problem.
PHP4 is perfectly happy being linked with the
MySQL 5
client libraries, it's the database server that
needs
to be 3.23. The SQL used in dotProject is legal
for
3.23, but not 5.
Then you haven't explained yourself very well,
because at the start of
this thread you were talking about a conflict
between the mysql 3 and
mysql 5 *clients*, not servers.
I haven't been able to verify for sure that using a
MySQL 5 client library against a MySQL 3.23 server is
supported. I can't find any references on the
MySQL.com site.
In any case, you can't install mysql5?-client and
mysql323-server together using the ports.
Typically, people installing this would have the web
server and the mysql server on the same machine, so
the best solution (other than dotproject finally
supporting modern versions of the software) would be
to link against mysql323-client. However, there is no
build problem with linking against mysql5?-client.
dotproject is a set of scripts.
--
Trying to get it to install MySQL 3.23 client seems
to
be stymied by the php4-mysql default dependency on
the
MySQL 5 client. I haven't actually figured out how
it
specifies this dependency, since the
php4-mysql/Makefile is very empty.
--
So, does it or does it not require the mysql 3.23
client in
php4-mysql and dotproject?
I don't know for sure. Practically speaking, for most
users, it does.
Your objection to doing an interim fix while I try to
figure out how to do what you suggest doesn't apply
though, because there is nothing broken at the package
build or linkage level. There is only a potential
protocol problem with using different versions of the
client and server together.
Copy the php4-mysql port to php4-mysql3 and make
the
presumably
trivial change to make it use mysql 3 instead of
whatever the default
is.
It's not trivial. The current Makefile is
trivial,
but a change to do what you're suggesting will
need to
be more complex.
Here's the current php4-mysql Makefile:
CATEGORIES= databases
MASTERDIR= ${.CURDIR}/../../lang/php4
PKGNAMESUFFIX= -mysql
.include ${MASTERDIR}/Makefile
The ${MASTERDIR}/Makefile doesn't refer to mysql
at
all.
Personally, I don't see how it knows it's supposed
to
link MySQL in there. Perhaps it's because PHP4
defaults to including MySQL support, so this isn't
really doing anything. I haven't read far enough
to
know for sure.
Look in bsd.php.mk for the rest.
More studying,
Fred
Kris
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/dotproject out of date and vulnerable
On Tue, Sep 19, 2006 at 06:49:52PM -0700, Fred Cox wrote: Then you haven't explained yourself very well, because at the start of this thread you were talking about a conflict between the mysql 3 and mysql 5 *clients*, not servers. I haven't been able to verify for sure that using a MySQL 5 client library against a MySQL 3.23 server is supported. I can't find any references on the MySQL.com site. In any case, you can't install mysql5?-client and mysql323-server together using the ports. Correct, because the software cannot coexist in the same install prefix. Typically, people installing this would have the web server and the mysql server on the same machine, so the best solution (other than dotproject finally supporting modern versions of the software) would be to link against mysql323-client. However, there is no build problem with linking against mysql5?-client. dotproject is a set of scripts. If there is no problem with using the mysql 5.x client, then just use mysql 5.x and be done with it. You need to figure out whether or not that is true. If it is false, then there's clearly a problem for you (since in the situation we've been discussing php4-mysql will be using mysql 5.x). This whole discussion came about because you were trying to look for a way to force everything (including php4-mysql) to link to mysql 3.x, which is currently impossible to achieve satisfactorily without further work on your part. Kris pgpWUYRqGF9nU.pgp Description: PGP signature
Re: FreeBSD Port: courier-imap-4.1.1,1
On Wed, Jun 21, 2006, at 19:09:38 -0400, Tamouh H. wrote: Hi Oliver, While attempting to install courier-imap on fresh FreeBSD 6.1 install, I encounter this error (seems file gdbm.h is missing): chochang# make install distclean === Building for courier-imap-4.1.1,1 gmake all-recursive gmake[1]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1' gmake all-gmake-check FOO=BAR gmake[2]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1' gmake[2]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1' Making all in numlib gmake[2]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/numlib' gmake all-am gmake[3]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/numlib' gmake[3]: Nothing to be done for `all-am'. gmake[3]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/numlib' gmake[2]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/numlib' Making all in md5 gmake[2]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/md5' gmake all-am gmake[3]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/md5' gmake[3]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/md5' gmake[2]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/md5' Making all in sha1 gmake[2]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/sha1' gmake all-am gmake[3]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/sha1' gmake[3]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/sha1' gmake[2]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/sha1' Making all in gdbmobj gmake[2]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/gdbmobj' gmake all-am gmake[3]: Entering directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/gdbmobj' Compiling gdbmobj.c In file included from gdbmobj.c:10: gdbmobj.h:11:18: gdbm.h: No such file or directory In file included from gdbmobj.c:10: gdbmobj.h:20: error: syntax error before GDBM_FILE gdbmobj.c: In function `gdbmobj_close': gdbmobj.c:33: error: structure has no member named `dbf' gdbmobj.c: In function `gdbmobj_open': gdbmobj.c:44: error: `GDBM_READER' undeclared (first use in this function) gdbmobj.c:44: error: (Each undeclared identifier is reported only once gdbmobj.c:44: error: for each function it appears in.) gdbmobj.c:50: error: `GDBM_WRCREAT' undeclared (first use in this function) gdbmobj.c:54: error: `GDBM_WRITER' undeclared (first use in this function) gdbmobj.c:58: error: `GDBM_NEWDB' undeclared (first use in this function) gdbmobj.c:63: error: structure has no member named `dbf' gdbmobj.c:70: error: structure has no member named `dbf' gdbmobj.c: In function `gdbmobj_store': gdbmobj.c:87: error: syntax error before dkey gdbmobj.c:90: error: `dkey' undeclared (first use in this function) gdbmobj.c:93: error: `dval' undeclared (first use in this function) gdbmobj.c:96: error: structure has no member named `dbf' gdbmobj.c:98: error: `GDBM_INSERT' undeclared (first use in this function) gdbmobj.c:98: error: `GDBM_REPLACE' undeclared (first use in this function) gdbmobj.c: In function `gdbmobj_exists': gdbmobj.c:103: error: syntax error before dkey gdbmobj.c:107: error: `dkey' undeclared (first use in this function) gdbmobj.c:110: error: structure has no member named `dbf' gdbmobj.c: In function `gdbm_dofetch': gdbmobj.c:166: error: syntax error before dkey gdbmobj.c:170: error: `dkey' undeclared (first use in this function) gdbmobj.c:173: error: `val' undeclared (first use in this function) gdbmobj.c:173: error: structure has no member named `dbf' gmake[3]: *** [gdbmobj.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/gdbmobj' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/gdbmobj' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/mail/courier-imap. Was there a solution to this? I'm trying to deploy a server and get clients moved on a real short time frame right now and am having the same compile errors with courier-imap. Thanks very much in advance. -Mark FreeBSD 6.1-RELEASE -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD Port: courier-imap-4.1.1,1
gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1/gdbmobj' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/mail/courier-imap/work/courier-imap-4.1.1' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/mail/courier-imap. Was there a solution to this? I'm trying to deploy a server and get clients moved on a real short time frame right now and am having the same compile errors with courier-imap. Thanks very much in advance. -Mark FreeBSD 6.1-RELEASE Hi Mark, This was Oliver fix: -Original Message- From: Oliver Lehmann [mailto:[EMAIL PROTECTED] Sent: June 22, 2006 5:04 AM To: Tamouh H. Subject: Re: FreeBSD Port: courier-imap-4.1.1,1 somehow gdbm.h was missing in /usr/local/include: Deinstalling /databases/gdbm and then reinstalling it again resolved the problem chochang# make deinstall === Deinstalling for databases/gdbm === Deinstalling gdbm-1.8.3_2 pkg_delete: file '/usr/local/include/gdbm.h' doesn't exist pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) chochang# make install === Installing for gdbm-1.8.3_2 === Generating temporary packing list === Checking if databases/gdbm already installed ./mkinstalldirs /usr/local/lib \ /usr/local/include /usr/local/man/man3 \ /usr/local/info /bin/sh ./libtool /usr/bin/install -c -o root -g wheel -c libgdbm.la /usr/local/lib/libgdbm.la /usr/bin/install -c -o root -g wheel -c .libs/libgdbm.so.3 /usr/local/lib/libgdbm.so.3 (cd /usr/local/lib rm -f libgdbm.so ln -s libgdbm.so.3 libgdbm.so) (cd /usr/local/lib rm -f libgdbm.so ln -s libgdbm.so.3 libgdbm.so) /usr/bin/install -c -o root -g wheel -c .libs/libgdbm.lai /usr/local/lib/libgdbm.la /usr/bin/install -c -o root -g wheel -c .libs/libgdbm.a /usr/local/lib/libgdbm.a ranlib /usr/local/lib/libgdbm.a chmod 644 /usr/local/lib/libgdbm.a -- Libraries have been installed in: /usr/local/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. -- install -o root -g wheel -m 444 -o bin -g bin gdbm.h \ /usr/local/include/gdbm.h install -o root -g wheel -m 444 -o bin -g bin ./gdbm.3 \ /usr/local/man/man3/gdbm.3 install -o root -g wheel -m 444 -o bin -g bin ./gdbm.info \ /usr/local/info/gdbm.info install-info --quiet /usr/local/info/gdbm.info /usr/local/info/dir === Compressing manual pages for gdbm-1.8.3_2 === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for gdbm-1.8.3_2 chochang# reinstalling gdbm should have fixed this. Please retry compiling courier-imap. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: courier-imap-4.1.1,1
Mark Kane wrote: On Wed, Jun 21, 2006, at 19:09:38 -0400, Tamouh H. wrote: Hi Oliver, While attempting to install courier-imap on fresh FreeBSD 6.1 install, I encounter this error (seems file gdbm.h is missing): please reinstall your gdm port and then try courier-imap again. -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: courier-imap-4.1.1,1
On Wed, Sep 20, 2006, at 06:16:30 +0200, Oliver Lehmann wrote: Mark Kane wrote: On Wed, Jun 21, 2006, at 19:09:38 -0400, Tamouh H. wrote: Hi Oliver, While attempting to install courier-imap on fresh FreeBSD 6.1 install, I encounter this error (seems file gdbm.h is missing): please reinstall your gdm port and then try courier-imap again. Thanks a million guys!!! Works great now. Just saved me a lot of stress tonight. -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
