fvwm themes instalation script error
Hi, I got this error trying to install fvwm-themes checking for fvwm-config... /usr/local/bin/fvwm-config checking for FvwmM4... /usr/local/libexec/fvwm/2.4.20/FvwmM4 configure: error: You have fvwm-2.4.20, which is not up to date You need at least fvwm-2.5.8 === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the /usr/ports/x11-themes/fvwm-themes/work/fvwm-themes-0.7.0/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/x11-themes/fvwm-themes. %pwd /usr/ports/x11-themes/fvwm-themes % === /usr/ports/x11-themes/fvwm-themes/work/fvwm-themes-0.7.0/config.log is atached === %ls /var/db/pkg GraphicsMagick-1.1.10 ilmbase-1.0.0_2 py25-cairo-1.4.0_1 ORBit2-2.14.10 imake-1.0.2_4,1 py25-gnome-2.20.0 OpenEXR-1.6.0 inputproto-1.4.2.1 py25-gobject-2.14.0 appres-1.0.1intltool-0.36.2 py25-gtk-2.12.0 apr-db42-1.2.8_2iso-codes-1.5 py25-libxml2-2.6.30 arts-1.5.8,1iso8879-1986_2 py25-numeric-24.2 aspell-0.60.5_2 ispell-3.2.06_18 py25-orbit-2.14.3 atk-1.20.0 jackit-0.103.0 python25-2.5.1_1 autoconf-2.13.000227_6 jasper-1.900.1_6 qt-3.3.8_6 autoconf-2.61_2 jbigkit-1.6 randrproto-1.2.1 autoconf-wrapper-20071109 jpeg-6b_4 rarian-0.6.0_1 automake-1.10_3 kbproto-1.0.3 recordproto-1.13.2 automake-1.4.6_4kdehier-1.0_11 renderproto-0.9.3 automake-1.5_4,1kdelibs-3.5.8 rgb-1.0.1 automake-1.6.3 koffice-1.6.3_3,2 rstart-1.0.2 automake-1.7.9 lcms-1.17,1 rsync-2.6.9_2 automake-1.8.5 libFS-1.0.0 ruby-1.8.6.111_1,1 automake-1.9.6_2libGL-7.0.1 samba-3.0.28,1 automake-wrapper-20071109 libGLU-7.0.1 samba-libsmbclient-3.0.28 autotools-20070905 libICE-1.0.4,1 scripts-1.0.1 avahi-0.6.21_1 libIDL-0.8.9_1 scrnsaverproto-1.1.0 avahi-app-0.6.21_1 libSM-1.0.3,1 sdocbook-xml-1.1,1 bash-3.2.25 libX11-1.1.3,1 sessreg-1.0.3 bdftopcf-1.0.1 libXScrnSaver-1.1.2 setxkbmap-1.0.4 beforelight-1.0.2 libXTrap-1.0.0 shared-mime-info-0.22_1 bison-2.3_3,1 libXau-1.0.3_2 showfont-1.0.1 bitmap-1.0.3libXaw-1.0.4,1 smproxy-1.0.2 bitstream-vera-1.10_4 libXcomposite-0.4.0,1 startup-notification-0.9_1 cairo-1.4.10_1 libXcursor-1.1.9 subversion-1.4.4_1 cdrtools-2.01_6 libXdamage-1.1.1 sudo-1.6.9.6 compositeproto-0.4 libXdmcp-1.0.2 t1lib-5.1.1_2,1 cups-base-1.3.5_2 libXevie-1.0.2 tiff-3.8.2_1 damageproto-1.1.0_2 libXext-1.0.3,1 trapproto-3.4.3 db42-4.2.52_5 libXfixes-4.0.3 twm-1.0.3_3 dbus-1.0.2_2libXfont-1.3.1_2,1 urlview-0.9_2 dbus-glib-0.74 libXfontcache-1.0.4 v4l_compat-1.0.20060801 desktop-file-utils-0.14 libXft-2.1.12 videoproto-2.2.2 djbfft-0.76_2 libXi-1.1.3,1 viewres-1.0.1 dmidecode-2.9 libXinerama-1.0.2,1 wv2-0.2.3_1 docbook-sk-4.1.2_4 libXmu-1.0.3,1 x11perf-1.4.1 docbook-xml-4.2_1 libXp-1.0.0,1 xauth-1.0.2 docbook-xml-4.3 libXpm-3.5.7 xbacklight-1.1 docbook-xml-4.4 libXprintAppUtil-1.0.1 xbiff-1.0.1 docbook-xsl-1.71.1_2libXprintUtil-1.0.1 xbitmaps-1.0.1 dri-7.0.1,2 libXrandr-1.2.2 xcalc-1.0.2 editres-1.0.3 libXrender-0.9.4 xclipboard-1.0.1 encodings-1.0.2,1 libXres-1.0.3_2 xclock-1.0.3 epiphany-2.20.1 libXt-1.0.5 xcmsdb-1.0.1 esound-0.2.38 libXtst-1.0.3 xconsole-1.0.3
Re: fvwm themes instalation script error
in message [EMAIL PROTECTED], wrote Siju George thusly... I got this error trying to install fvwm-themes checking for fvwm-config... /usr/local/bin/fvwm-config checking for FvwmM4... /usr/local/libexec/fvwm/2.4.20/FvwmM4 configure: error: You have fvwm-2.4.20, which is not up to date You need at least fvwm-2.5.8 === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the ... fvwm-imlib-2.4.20_1 As the error message implies you need to install the development version of fvwm from x11-wm/fvwm2-devel (currently 2.5.23) instead of the stable version. - Parv -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fvwm themes instalation script error
Hi, according to the ports tree you need to install fvwm2-devel, which is currently at 2.5.24_1 HTH Christian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports system woes
Garrett Cooper wrote: We're rehashing the discussion made last year around June - July. Indeed. We came to the conclusion that BDB should be used, as no other DB backend / API exists in the base system (currently), and porting SQLLite (while nice) appeared to be non-trivial to port Are you kidding? The patch files are totally trivial modifications, to include stdlib.h. The bigger one is in Makefile.in to take into account these ones. and got a lot of unhappy responses from folks. This is true. A lot of people expressed aversion against SQL, by itself. However it should not be bad to evaluate a solution based on BerkeleyDB, another one on sqlite, and chose based on merit, not on aversions. What is the simplest to use by the programmer writing pkg_* tools, what offers the best performance and data organization, etc. At the moment portupgrade uses a BerkeleyDB, are you convinced by the result? In particular an obvious fact is that there are constant troubles when the DB version number changes or the ruby adapter changes. One may expect that no such problems will occur with a very stable and standardized language like it is offered by sqlite. If this argument is correct, it is quite strong, in my opinion, because i don't expect much performance difference otherwise. There is also the question of atomicity and locking which is particularly important in this context. It would be useful to compare what the BdB in the base system has to offer compared to sqlite - because comparing to what the most recent versions of bdb in the ports can do has a different bearing on the question. -- Michel TALON ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmaster and BROKEN ports
Doug Barton [EMAIL PROTECTED] 2008-03-26: Willy Picard wrote: portupgrade simply ignores BROKEN ports during a portupgrade -a. I am not even asking about a similar behaviour for portmaster. I wanted just to ask if an option allows to do the same. If no such an option exists, I think that its addition to the functionality of portmaster may be worth considering. I think it's important for users to know when their ports go into a BROKEN state, so ignoring them is not an option. If a user actually wants to ignore a port that is BROKEN, the +IGNOREME mechanism is available, as you pointed out. Of course the user wants to be notified of all ports which cannot be upgraded for some reason (broken, marked BROKEN, removed/missing origin, etc.), but forcing the upgrade to abort because of a problem with a single port does not make sense. It means that portmaster can only be run successfully if all the installed ports are in a 100% upgradable state, which in my experience is basically almost never, except on production servers with only a few well-maintained ports installed. To keep a box current with portmaster, I have to manually mark each of the non-upgradable ports with +IGNOREME files after portmaster bails out, and restart portmaster. I will then have to periodically check back manually whether the problems went away in the meantime. This is unacceptable for me; too much manual intervention. I would very much prefer to have an option that tells portmaster to skip non-upgradable ports and those that depend on them, and notify me in form of a concise, greppable list after the portmaster run. This is actually the number one reason I switched back to portupgrade. Other than that, portmaster would be the tool of my choice. -Dan -- Daniel Roethlisberger [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Referencing older entries in ports/UPDATING may be bad practice
Referencing old entries in ports/UPDATING that contain the commands, options, etc. isn't completely safe because those options may change. In the case of portupgrade(1), at the following options changed between pkgtools-2.0.1 and pkgtools-2.4.3: 2.0.1: -c --clean Do ``make clean'' before each build. This is the default behavior. See the -w option below. -C --cleanupDo ``make clean'' after each installation. This is the default behavior. See the -W option below. -q --noconfig Do not read the configuration file - $PREFIX/etc/pkgtools.conf. 2.4.3: -c --config Run ``make config-conditional'' before everything for all tasks. -w option below. -C --force-config Run ``make config'' before everything for all tasks. -q --quiet Do not display a message when -N specified and there is already installed package. It doesn't bite to make each entry a little bit more self-contained at least when it comes to the sequence of commands to be run. Though I haven't yet found a single issue with current practice, it's better to feel safe than to worry at the possibility, excuse me if it's just me ;) Safe for users and developers alike. ___ 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: MailScanner-4.67.6
:-) I love FreeBSD and its community!!! Thank you for being so responsive! Paul Pathiakis From: Koopmann, Jan-Peter [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2008 10:14 AM To: Paul Pathiakis Cc: [EMAIL PROTECTED] Subject: RE: FreeBSD Port: MailScanner-4.67.6 New version was committed today. Update your port tree please. Mit freundlichen Grüßen Jan-Peter Koopmann Dipl.-Wirtschaftsinformatiker Geschäftsführer From: Paul Pathiakis [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2008 2:44 PM To: Koopmann, Jan-Peter Cc: [EMAIL PROTECTED] Subject: FreeBSD Port: MailScanner-4.67.6 Hi, It seems that the latest p5-Mail-Tools in the ports tree causes a problem with MailScanner. This has, apparently, been documented in many Linux distros as well. I'm not sure if it's a problem with MailScanner or with the perl module. However, I couldn't get it to run until I went to the previous version of p5-Mail-Tools 1.77. Then, it ran just fine. I was on FreeBSD 6.2 - p2. Thank you, Paul Pathiakis -- Seceidos GmbHCo. KG Robert-Bosch-Str. 7 64293 Darmstadt / Germany E-Mail: [EMAIL PROTECTED] http://www.seceidos.de http://www.seceidos.de/ Tel: +49 (6151) 66843-43 Fax: +49 (6151) 66843-52 SIP: [EMAIL PROTECTED] Skype: jan-peter.koopmann HRA 7206, Amtsgericht Darmstadt persönlich haftende Gesellschafterin: Seceidos Verwaltungs GmbH, Grafrath, HRB 158903, Amtsgericht München Geschäftsführer: Robert Hochrein, Jan-Peter Koopmann Seceidos FZE Emirates Towers, Level 41 Sheikh Zayed Road P.O. Box 31303 Dubai, UAE http://www.seceidos.com http://www.seceidos.com/ Tel: +971 (4) 3197741 Fax: +971 (4) 3197742 SIP:[EMAIL PROTECTED] Skype: jan-peter.koopmann ___ 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: MailScanner-4.67.6
New version was committed today. Update your port tree please. Mit freundlichen Grüßen Jan-Peter Koopmann Dipl.-Wirtschaftsinformatiker Geschäftsführer From: Paul Pathiakis [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2008 2:44 PM To: Koopmann, Jan-Peter Cc: [EMAIL PROTECTED] Subject: FreeBSD Port: MailScanner-4.67.6 Hi, It seems that the latest p5-Mail-Tools in the ports tree causes a problem with MailScanner. This has, apparently, been documented in many Linux distros as well. I'm not sure if it's a problem with MailScanner or with the perl module. However, I couldn't get it to run until I went to the previous version of p5-Mail-Tools 1.77. Then, it ran just fine. I was on FreeBSD 6.2 - p2. Thank you, Paul Pathiakis -- Seceidos GmbHCo. KG | Tel: +49 (6151) 66843-43 Robert-Bosch-Str. 7 | Fax: +49 (6151) 66843-52 64293 Darmstadt/Germany | http://www.seceidos.de | SIP: [EMAIL PROTECTED] Skype: jan-peter.koopmann E-Mail: [EMAIL PROTECTED] HRA 7206, Amtsgericht Darmstadt persönlich haftende Gesellschafterin: Seceidos Verwaltungs GmbH, Grafrath HRB 158903, Amtsgericht München Geschäftsführer: Robert Hochrein, Jan-Peter Koopmann Seceidos FZE | Tel: +971 (4) 3197741 Emirates Towers, Level 41 | Fax: +971 (4) 3197742 Sheikh Zayed Road | P.O. Box 31303 | SIP: [EMAIL PROTECTED] Dubai, UAE http://www.seceidos.com Skype: jan-peter.koopmann E-Mail: [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: portmaster and BROKEN ports
Daniel Roethlisberger wrote: Of course the user wants to be notified of all ports which cannot be upgraded for some reason (broken, marked BROKEN, removed/missing origin, etc.), but forcing the upgrade to abort because of a problem with a single port does not make sense. It may not make sense to you, but since I have no way of knowing what the user wants to do with a broken port unless they actually take some kind of action, it makes perfect sense to me. It means that portmaster can only be run successfully if all the installed ports are in a 100% upgradable state, If you're talking about running 'portmaster -a' without ever having to pay attention to what happens, then yes, you're probably right. But there are a lot of other ways to use portmaster, and a lot of users that do not have as many poorly maintained ports as you seem to be stuck with. :) To keep a box current with portmaster, I have to manually mark each of the non-upgradable ports with +IGNOREME files after portmaster bails out, and restart portmaster. I will then have to periodically check back manually whether the problems went away in the meantime. This is unacceptable for me; too much manual intervention. I would very much prefer to have an option that tells portmaster to skip non-upgradable ports and those that depend on them, and notify me in form of a concise, greppable list after the portmaster run. That sounds like a great idea, if I ever find the time (or a sponsor) to write that code, I think it would be a nice addition. (And btw, I would argue that ignoring updates for ports that depend on a broken port is not necessarily the best default action.) Meanwhile, you're talking about two entirely different problem sets here. In regards to the second issue (what happens when a port you +IGNOREME'ed is no longer broken) portmaster already has the ability to notify you that an update is ready for an ignored port, and will prompt you to update it even if there is an +IGNOREME file (assuming you're not using -u). This is actually the number one reason I switched back to portupgrade. That's actually Ok with me. :) Portupgrade is a good tool, and it has a lot of features that portmaster does not, and probably will never have. I have said many times that I do not intend portmaster to be a portupgrade replacement. If portupgrade meets your needs better, then by all means you should use it. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
using pkgdb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm using pkgdb because I wanted to try portupgrade, and it required it. My problem is that it's doing procedures, asking for a decision on my part, but I can't make any guess how to answer it, because the prompt is fairly meaningless to me. Here is an example of what I'm seeing: Stale dependency: someportname-1.1.1 - differentportname-1.1.1 (differentportname): 3rdportname-1.1.1 ? ([y]es/[n]o/[a]ll) [yes] I haven't the least idea what the Y/N/A is referring to, what sort of action I am causing or allowing. I tried the man page on pkgdb, but I didn't see that sort of message in that page. Sure hope you can give me a hint (and, as a hint, this might be a good time to fix that fairly useless prompt). -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH69qyz62J6PPcoOkRAkLKAJ4pV/vKgKv4aojyYymSPaclGHonzgCfZD9a lN12HYVWg/m22k700ubkokA= =BMlj -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]
RE: FreeBSD Port: MailScanner-4.67.6
Portupgrade -a -r -p took care of everything after my cvsup. Ports were about 3-4 months out of date. Once updated and restarted, everything worked fine. (portupgrade loaded or upgraded all the requirements you mention below.) How can people not love this OS? I can't wait to migrate some of the machines in my house to 7.0. Thanks again to all! Paul Pathiakis -Original Message- From: Johan Hendriks [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2008 10:16 AM To: Paul Pathiakis Cc: freebsd-ports@freebsd.org Subject: RE: FreeBSD Port: MailScanner-4.67.6 Hi, It seems that the latest p5-Mail-Tools in the ports tree causes a problem with MailScanner. This has, apparently, been documented in many Linux distros as well. I'm not sure if it's a problem with MailScanner or with the perl module. However, I couldn't get it to run until I went to the previous version of p5-Mail-Tools 1.77. Then, it ran just fine. I was on FreeBSD 6.2 - p2. Thank you, Paul Pathiakis Well with the version 4.64.4 i had that problem, i could not update p5-Mail-Tools to 2.02 Now with version 4.67.6 it works just fine. Also make sure you have devel/p5-IO installed, It is needed now by MailScanner. It was not in the ports for some time but i send a pr and p5-IO is added to the build of MailScanner now Regards, Johan Hendriks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE : problem building asterisk
Dear Puchar! Here is what you should did before: a) if you 're installing from ports: http://www.cupovoip.com/docs/asterisk-installation-freebsd-english.html b) from source http://wiki.sangoma.com/wanpipe-linux-asterisk-install cheers!! Tracy Wojciech Puchar [EMAIL PROTECTED] a écrit : any idea why? did make config with | ++ | | | [X] OGGVORBISEnable Ogg Vorbis support | | | | [ ] ODBC Enable ODBC support | | | | [ ] POSTGRES Enable PostgreSQL support | | | | [ ] RADIUS Enable RADIUS accounting support| | | | [X] SNMP Enable SNMP support | | | | [X] H323 Enable H.323 support | | | | [X] FREETDS Enable FreeTDS support | | | | [X] JABBER Enable Jabber and Gtalk support | | | | [X] SQLITE Enable SQLITE support | | | | [X] CODEC_PATCH Apply codec negotiation patch | | | | [ ] ZAPTEL Enable Zaptel support | | === Building for asterisk-1.4.18.1 menuselect/menuselect --check-deps menuselect.makeopts Generating embedded module rules ... gmake[1]: Nie ma nic do zrobienia w `all'. gmake[1]: Nie ma nic do zrobienia w `all'. gmake[1]: Nie ma nic do zrobienia w `all'. c++ -DNDEBUG -I../../include -include ../../include/asterisk/autoconfig.h -fPIC -O1 -I/usr2/ports/devel/pwlib/work/ptlib_v1_12_0/include -I/usr/local/include -DP_USE_PRAGMA -D_REENTRANT -pthread -fno-exceptions -O1 -I/usr2/ports/devel/pwlib/work/ptlib_v1_12_0/include -I/usr/local/include -Wall -DNDEBUG -I/usr/local/share/pwlib//include -DPTRACING -I/usr/local/include/openh323 -Os -pipe -O1 -I/usr2/ports/devel/pwlib/work/ptlib_v1_12_0/include -I/usr/local/include -O1 -I/usr2/ports/devel/pwlib/work/ptlib_v1_12_0/include -I/usr/local/include -c ast_h323.cxx -o ast_h323.o ast_h323.cxx: In destructor `virtual MyProcess::~MyProcess()': ast_h323.cxx:194: error: `timerChangePipe' was not declared in this scope gmake[2]: *** [ast_h323.o] B³±d 1 gmake[1]: *** [h323/libchanh323.a] B³±d 2 gmake: *** [channels] B³±d 2 *** Error code 2 Stop in /usr2/ports/net/asterisk. *** Error code 1 Stop in /usr2/ports/net/asterisk. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] Coko Tracy MIRINDI MUSAZA mobiles: 00242 576 14 00Congo 00243 81 250 0472 RDC www.airnetcg.net - Envoyé avec Yahoo! Mail. Capacité de stockage illimitée pour vos emails. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: There is no way to know what port options mean (in general)
On Wed, Mar 26, 2008 at 03:22:52PM +0100, Pav Lucistnik wrote: Wesley Shields p??e v st 26. 03. 2008 v 10:18 -0400: Sounds to me like you are thinking of including the description in the dialog. This sounds like a good idea to me and is something I can look into doing instead of my proposal. Yes, that was my thought, it must be easily visible in the blue screen, otherwise it will not be seen, most of the time. Something which would add a three line textbox below the dialog window, listing a long description for the item currently under the cursor. I can see it already! :) Can you code it? As a first pass I've got an almost working skeleton which uses --hfile and pulls the descriptions from OPTIONS variable (using a 4th field). It also adds --hline Please use ? for a detailed description to the dialog call. I need to clean it up and make it handle the case where the 4th field is not there. I'm going on a mini-vacation in an hour but will hopefully finish it up early next week. It's not quite what you were expecting but I'm not sure how to make dialog show two windows at once - admittedly I have not looked too hard at that. I'll post a final patch when I have it ready. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: dbmail-2.2.8
Hi,
The dbmail port has not been updated in a while. There are now two
stable version after the one in the port - 2.2.9 and 2.2.10, which fix
important bugs.
I'm sending you attache modified Makefile and distinfo files if you'll
be kind enough to upgrade that port.
Thanks very much in advance!
Kind regards,
Doichin Dokov
NetOne - Silistra
Bulgaria
MD5 (dbmail-2.2.10.tar.gz) = cd255326f410848e27e0a82a43fa2424
SHA256 (dbmail-2.2.10.tar.gz) =
f890167073498d87ea0ce374af2cf0498cfd7aa1af7aeb330726d1910de951b6
SIZE (dbmail-2.2.10.tar.gz) = 900636
# New ports collection makefile for:dbmail
# Date created: 07/26/2003
# Whom: Clement Laforet [EMAIL PROTECTED]
#
# $FreeBSD: ports/mail/dbmail/Makefile,v 1.37 2007/12/18 23:18:56 miwi Exp $
#
PORTNAME= dbmail
PORTVERSION=2.2.10
CATEGORIES= mail
MASTER_SITES= http://www.dbmail.org/download/2.2/
MAINTAINER= [EMAIL PROTECTED]
COMMENT=An SQL database-based mail system (POP3 and IMAP)
LIB_DEPENDS=gmime-2.0.4:${PORTSDIR}/mail/gmime2
CONFLICTS= dbmail-*-2.0.* dbmail-2.1.*
OPTIONS=MYSQL Build with MySQL support on \
POSTGRESQL Build with PostgreSQL support off \
SQLITE Build with SQLite support off \
SIEVE Build w. support for Sieve mail sorting
language off \
LDAPBuild with support for LDAP authentication off
USE_AUTOTOOLS= libtool:15
USE_GMAKE= YES
USE_GCC=3.2+
USE_LDCONFIG= ${PREFIX}/lib/dbmail
USE_RC_SUBR=dbmail-pop3d.sh dbmail-lmtpd.sh dbmail-imapd.sh
dbmail-timsieved.sh
USE_GNOME= glib20 pkgconfig
USE_OPENSSL=YES
CFLAGS+=-fPIC -I${LOCALBASE}/include ${PTHREAD_CFLAGS}
LDFLAGS+= -L${LOCALBASE}/lib ${PTHREAD_LIBS}
CONFIGURE_ENV+= LDFLAGS=${LDFLAGS} LOCALBASE=${LOCALBASE}
CONFIGURE_ARGS+=--with-pkglibdir=${LOCALBASE}/lib/dbmail
MAKE_ARGS+= mandir=${MANPREFIX}/man
PORTDOCS= AUTHORS BUGS COPYING INSTALL NEWS README \
README.aliases README.exim README.ldap \
README.postfix README.qmail README.sieve \
README.smtp README.solaris README.usermap \
THANKS
MAN1= dbmail-smtp.1 dbmail.1
MAN5= dbmail.conf.5
MAN8= dbmail-export.8 dbmail-imapd.8 dbmail-lmtpd.8 \
dbmail-pop3d.8 dbmail-sievecmd.8 dbmail-timsieved.8 \
dbmail-users.8 dbmail-util.8
MANCOMPRESSED= no
SUB_FILES= pkg-message
PLIST_SUB+= PORTNAME=${PORTNAME}
.if defined(NOPORTDOCS)
PLIST_SUB+= PORTDOCS=@comment
.else
PLIST_SUB+= PORTDOCS=
.endif
.include bsd.port.pre.mk
.if !defined(WITHOUT_MYSQL)
CONFIGURE_ARGS+=--with-mysql
USE_MYSQL= YES
DATABASE+= mysql
PLIST_SUB+= MYSQL=
.else
PLIST_SUB+= MYSQL=@comment
.endif
.if defined(WITH_POSTGRESQL)
CONFIGURE_ARGS+=--with-pgsql
USE_PGSQL= yes
DATABASE+= postgresql
PLIST_SUB+= PGSQL=
.else
PLIST_SUB+= PGSQL=@comment
.endif
.if defined(WITH_SQLITE)
CONFIGURE_ARGS+=--with-sqlite
USE_SQLITE= yes
DATABASE+= sqlite
PLIST_SUB+= SQLITE=
.else
PLIST_SUB+= SQLITE=@comment
.endif
.if defined(WITH_SIEVE)
CONFIGURE_ARGS+=--with-sieve=${LOCALBASE}/include
LIB_DEPENDS+= sieve.1:${PORTSDIR}/mail/libsieve
PLIST_SUB+= SIEVE=
.else
PLIST_SUB+= SIEVE=@comment
.endif
.if defined(WITH_LDAP)
CONFIGURE_ARGS+=--with-auth-ldap=${LOCALBASE}/include
USE_OPENLDAP= yes
PLIST_SUB+= LDAP=
.else
PLIST_SUB+= LDAP=@comment
.endif
.if defined(WITHOUT_MYSQL) !defined(WITH_POSTGRESQL) !defined(WITH_SQLITE)
IGNORE=requires at least one database backend selected. Run 'make config'
.endif
post-patch:
@${FIND} ${WRKSRC} -name CVS -type d | ${XARGS} ${RM} -fr
@${FIND} ${WRKSRC} -name *.orig -type f | ${XARGS} ${RM} -fr
post-configure:
@${REINPLACE_CMD} -i.orig
's!/etc/dbmail.conf!${PREFIX}/etc/dbmail.conf!g' \
${WRKSRC}/dbmail.h
# remove leftovers which are not removed by some revisions of port
# fixes the `Shared object libpgsqldbmail.so.0 not found, required by
libdbmail.so.0' error.
pre-install:
@for f in 'a' 'la' 'so' 'so.0'; do \
if [ -f ${PREFIX}/lib/libdbmail.$$f ] ; then \
${RM} ${PREFIX}/lib/libdbmail.$$f; \
fi; \
done
post-install:
@${INSTALL_DATA} ${WRKSRC}/dbmail.conf ${PREFIX}/etc/dbmail.conf-dist
@if [ ! -f ${PREFIX}/etc/dbmail.conf ] ; then \
${CP} -p ${PREFIX}/etc/dbmail.conf-dist ${PREFIX}/etc/dbmail.conf; \
fi
@${MKDIR} ${DATADIR}
@for f in ${DATABASE}; do \
${MKDIR} ${DATADIR}/$$f ; \
${INSTALL_DATA} ${WRKSRC}/sql/$$f/* ${DATADIR}/$$f; \
done
.if !defined(NOPORTDOCS)
@${MKDIR} ${DOCSDIR}
@cd ${WRKSRC} ${INSTALL_DATA} ${PORTDOCS} ${DOCSDIR}
.endif
@${CAT} ${PKGMESSAGE}
.include
Re: Utility for safe updating of ports in base system
Sorry for the late reply, catching up on emails ... On Thu, 20.03.2008 at 23:32:49 +0100, Pav Lucistnik wrote: Doug Barton píše v čt 20. 03. 2008 v 13:12 -0700: Pav Lucistnik wrote: Doug Barton píše v c(t 20. 03. 2008 v 01:05 -0700: On Thu, 20 Mar 2008, Michel Talon wrote: i would venture to say that such an utility should be able to upgrade things based of *binary* packages, and consequently that portmaster is not a suitable candidate. That ability is not included in the current requirements document, and was not specifically mentioned the last time we had the discussion on the list. If the portmgr folks intend that to be a requirement, the current ideas list entry should be amended. Yes, I think ability to work with packages on a remote FTP site with no local /usr/ports, solely relying on an INDEX file, is a solid must have requirement. I have added that to the entry in the Ideas page. Amen. To give people in this thread an idea for a very important use case for businesses running on FreeBSD: We have a build machine set up, that will build all our required ports on certain releases with our custom make.conf settings. All these releases are revisioned themselves, so we can always tell which exact version of what binaries where present on those systems. Our FreeBSD machines themselves do not have any /usr/ports and don't (can't) mount it via NFS. They solely have to rely on pkg_add(1) using FTP to update their packages. This is where an automatic tool would come in handy :) Some people mentioned license issues with certain ports that would disallow the package building: These issues are non-existant if you are talking about in-house distribution only. All our jdks are pkg_add(1)ed and would love to be upgraded just the same. I would be more sympathetic to this idea if we could somehow push security-sensitive package builds up to the top of the list (so they would be available ASAP), but the last time I inquired about this I was told it isn't possible. It's not possible at the moment. There are dreams of having an on-commit action that would trigger a rebuild of the changed port and only the changed port on all platforms. But I feel this would be fairly hard to implement inside the current pointyhat framework. I hacked something together once, that would more or less make it trivial to implement this. I used make(1) (of course) to get the package dependancy in the form foo.tbz: bar.tbz baz.tbz # black magic to build foo.tbz inside clean tree This immediately allows one to use 'make -j64 openoffice.org.tbz' and one could add the following dependancy, to have the port rebuild after every commit (to Makefile, or some suitable file of the port) foo.tbz: category/foo/Makefile Though this will trigger quite a hefty rebuild, if you ever touch the Makefile of the gettext port for example. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/121887: security/fwtk fails to build with X11=off option setting
Synopsis: security/fwtk fails to build with X11=off option setting Responsible-Changed-From-To: pirzyk-freebsd-ports Responsible-Changed-By: pirzyk Responsible-Changed-When: Thu Mar 27 22:13:47 UTC 2008 Responsible-Changed-Why: Patch looks good to me, please commit at your convience. Thanks. http://www.freebsd.org/cgi/query-pr.cgi?pr=121887 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Unable to build cups-base-1.3.6_1
Hi Frank, On Wed, Mar 26, 2008 at 06:17:58AM -0700, Frank Mayhar wrote: pthread functions. I fixed it by putting LIBS=-lpthread in my environment before rebuilding the port. This is a kludge, though; the port maintainer needs to fix this. Worked well here, thanks! Regards Raphael Becker -- Raphael Becker [EMAIL PROTECTED] http://rabe.uugrn.org/ GnuPG:E7B2 1D66 3AF2 EDC7 9828 6D7A 9CDA 3E7B 10CA 9F2D .|.|.|.|.|.|.|.. pgpCpoCySGBdi.pgp Description: PGP signature
Re: There is no way to know what port options mean (in general)
Wesley Shields píše v čt 27. 03. 2008 v 15:58 -0400: I can see it already! :) Can you code it? As a first pass I've got an almost working skeleton which uses --hfile and pulls the descriptions from OPTIONS variable (using a 4th field). It also adds --hline Please use ? for a detailed description to the dialog call. Cool. It's not quite what you were expecting but I'm not sure how to make dialog show two windows at once - admittedly I have not looked too hard at that. It might not be possible with existing dialog(1). Anyway, thanks for the effort, I'm looking forward to nexxt week for a final patch. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] The rule of software licences: If it doesn't fit on your screen, it's probably too complex to understand. signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: [patch] pkg_delete(1) speedup
Roman Divacky wrote: On Wed, Mar 26, 2008 at 05:18:29PM +0100, Pav Lucistnik wrote: You might have noticed a thread on the mailing list called ports system woes. The submitter pointed out an inefficiency in pkg_delete routine, that parses the whole /var/db/pkg over and over again for every dependency of a package being removed. Attached is a patch by rdivacky that implements the idea of looking up all the values in a single pass over /var/db/pkg content. I hacked a slightly better patch that coveres a part of pkg_add too.. please review/test on: www.vlakno.cz/~rdivacky/pkg_tools.patch comments, benchmarks more than welcome! A) this is massively cool stuff, thanks for taking this on. :) B) you should probably do two versions of the patch, one with style(9)-only changes, and one without. The former makes it much easier to review the actual changes, and would speed your path to getting it in the tree. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Comments please: Ports 2.0 SoC application to Google
Abstract: Ports 2.0 is designed to be a drop in replacement for the FreeBSD ports system that incorporates the lesson learned from Peter Miller's Recursive Make Considered Harmful, http://aegis.sourceforge.net/auug97.pdf. The SoC portion of the project will be to create the engine and demostrate its capabilities by doing a ground up install and maintaince of the x11/xorg metaport. The implementation it self will be in C++ and use Aegis/Cook/FHist as the development environment. The design is meant to be extensible via plugins and embedded modules. After much field testing and completion of the complete project it is hoped Ports 2.0 will replace the current ports system. A hoped for side effect of using Aegis/Cook as the dependency management and configuration control systems is, they will be used more widely in the FreeBSD community. This project has been discussed at length on the freebsd-ports@freebsd.org mailing list and while the original team disbanded for logistical reasons Ports 2.0 will be tightly coupled with Alejandro Pulver's [EMAIL PROTECTED] work on his ports to do list maintained at http://wiki.freebsd.org/PortsToDo. Specifically the main work for the SoC portion of Ports 2.0 will come under items 3.1 and 5.x of the to do list. Kip Macy [EMAIL PROTECTED] has agreed to be the mentor for the project if accepted as a SoC project provided that no other suitable mentor can be found. For detailed development schedule see the Detailed Description portion of the this application. I have used FreeBSD since 1995 and before returning to school worked as a research scientist and director of RD for a very early pioneer of streaming media which was a 100% FreeBSD shop and required substantial modifications to the network stack and file subsytems of the kernel (most of which have been since incorporated into the mainstream TCP/IP stack/kernel and/or made unnecessary by them). See resume for more detail. Detailed Description: Please refer to abstract for general description of Ports 2.0. Key Features: 1. Avoidance of all issues raised in Recursive Make Considered Harmful 2. Maintain 100% compatibility with current ports system, portmaster/portupgrade and per project make files. 3. Provide a documented API for making modules and plugins 4. Document the theory behind the design so as to allow for faithful use of it 5. For ports not buildable by ports 2.0 (yet) fall back to the current ports system and/or portmaster/portupgrade automatically 6. Demonstrate on a very small subset of ports (for example sys/fusefs-ntfs and all it's dependabilities) the ability to trivially implement items 5.1, 5.5, 5.11 (awareness of updated base system only) from the to do list. Key Milestones and deadlines: MilestoneDeadline Complete the build skeletonWeek 1 Complete the graph libraryWeek 3 Dependency scanningWeek 5 Demonstration of dry run over xorg andWeek 6 items from feature 6 Demonstration of building an Week 7 non-cyclical ports graph Alpha test of xorg buildWeek 9 Beta test of xorg buildWeek 11 Complete API and theoretical Week 12 documentation ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
