Re: Dead projects in ports tree
On Mon, Mar 2, 2009 at 3:34 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: --On Monday, March 02, 2009 16:36:38 -0600 David E. Thiel l...@freebsd.org wrote: While I'm in favor of removing useless ports, there are several projects which are simply done, and lack of development doesn't mean they're obsolete or useless. I completely agree. So long as a port is being used and people find it useful, I think it would be a mistake to remove those ports. In fact I suspect it wouldn't be long before someone was submitting a PR to reinstate the port. Perfect example is converters/unix2dos, last updated in 2003 and converters/mpack, last updated in 2006. I still use both, and I would be irritated if they were removed from ports. A lack of development activity != a lack of usefulness I agree for projects like that that are feature complete. However, projects like xmms drag on the use of gtk 1.2 and will soon be out of date in terms of file formats, decoding capability, etc. Then again I suppose when that day comes xmms will be marked busted and eventually shuffled out of the tree, so I'll shut my trap about that :). openquicktime is another thing though: it's not useful for decoding today's quicktime videos because Apple's vastly updated the quicktime movie format -- thus unless someone's using it for some ancient format that's no longer used in mainstream, I personally don't understand the need for it in the tree. Also, I remember various security issues being reported with openquicktime in Gentoo Linux back a few years ago (when I used it religiously), so I really wonder how safe some of the 3rd party software is that is available via pkg / ports and is extremely out-of-date. Same with realplayer (or helix, or whatever it evolved into...). I'm just trying spark some interest in reducing the number of stale/unmaintainable ports in the tree because we have a large number of ports that aren't cared for like they should be :(. Thanks, -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Dead projects in ports tree
On Tue, Mar 3, 2009 at 10:26 AM, Garrett Cooper yanef...@gmail.com wrote: On Mon, Mar 2, 2009 at 3:34 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote: I completely agree. So long as a port is being used and people find it useful, I think it would be a mistake to remove those ports. In fact I suspect it wouldn't be long before someone was submitting a PR to reinstate the port. Perfect example is converters/unix2dos, last updated in 2003 and converters/mpack, last updated in 2006. I still use both, and I would be irritated if they were removed from ports. A lack of development activity != a lack of usefulness I agree for projects like that that are feature complete. However, projects like xmms drag on the use of gtk 1.2 and will soon be out of date in terms of file formats, decoding capability, etc. Then again I suppose when that day comes xmms will be marked busted and eventually shuffled out of the tree, so I'll shut my trap about that :). And what? Until gtk+-1.2 removed from ports, the xmms perfectly able to compile and run, at least from the gtk+ dependency side. Anyone, who don't like gtk-1.2 installed may just don't install both xmms and gtk+-1.2, just like me. Personal preferences are just personal preferences and no more. About file formats: my 5 years hardware dvd player also has limited decoding capability and formats support in comparison with today ones, but these capabilities are enough for me. And it still work. Now question: why I need to replace it if all just works and fits my requirements? The same logic may be applied to software too: why drop/replace if it just works? When it xmms occur to be uncompiliable or unable to run -- then yes, it may be reason to abandon it. But when it works ... see no reasons to remove. Frankly, I would glad to see absolutelly another discussion: not about dropping software that works (and as far as I understand, which port is maintained), but about making needed but broken software work again (e.g. valgrind, which is compiliable, but absolutelly not runnable since freebsd-7.0, and unfortunatelly has no replacement...) -- Andrew W. Nosenko andrew.w.nose...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Dead projects in ports tree
On Mon, Mar 2, 2009 at 7:36 PM, David E. Thiel l...@freebsd.org wrote: On Sat, Feb 28, 2009 at 04:05:56PM -0800, Garrett Cooper wrote: multimedia/openquicktime - no movement in CVS / SVN for 1+ years; no releases in the past 3 years I'll continue posting more items to this thread as I find them... Thanks, -Garrett xmms looks completely dead now. Can someone confirm or deny this fact? While I'm in favor of removing useless ports, there are several projects which are simply done, and lack of development doesn't mean they're obsolete or useless. The logic above would seem to suggest we should remove qmail too. I would like to hear what people feel the best method for getting rid of unused and irrelevant ports, though -- bump portrevision and mark BROKEN for a few months? Qmail doesn't have a new version for a long time, i know, but new version of patch collection are released, like you can see las spamcontrol 2.5.x, and author is working on 2.6.x with a lot of new features, so, i don't consider qmail a dead project at all. And, there are a good number of qmail users, i don't think it's a good idea remove this port, i'm maintaining it for some years and i can still maintain and keep it working on ports infrastructure. -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Configuring 'RUN_DEPENDS'
A port I am creating has a RUN_DEPENDS of either 'curl' or 'wget'. I have tried several times to write some sort of test in the make file to determine if one or the other were installed, and if neither then to install 'curl'. I suppose I could create an OPTIONS to install one or the other; however, I have not gotten that to work correctly either. I looked at Postfix's Makefile, and got a few ideas from it; however, not enough to get what I want to work. The port will also require Clamav, either the standard port or the devel one. Therefore I have two run dependencies to adjust. Use the one available or install one if neither is all ready installed. I tried Googling and the Porters Handbook, but I cannot find what I am looking for. Is it possible? I assume it must be. A regular 'if' or 'case' statement I would normally use does not work in a make file. -- Jerry ges...@yahoo.com Gratitude, like love, is never a dependable international emotion. Joseph Alsop signature.asc Description: PGP signature
Re: Dead projects in ports tree
On Tue, Mar 03, 2009 at 11:40:42AM +0200, Andrew W. Nosenko wrote: Frankly, I would glad to see absolutely another discussion: not about dropping software that works (and as far as I understand, which port is maintained), but about making needed but broken software work again (e.g. valgrind, which is compiliable, but absolutelly not runnable since freebsd-7.0, and unfortunatelly has no replacement...) Well, it all depends on how much work volunteers are willing to do. fwiw, I periodically send out email about broken ports (as evaluated on i386-current): http://docs.freebsd.org/cgi/mid.cgi?20090126081726.DBA671CC6F A less verbose, but constantly updated, version is at http://portsmon.freebsd.org/portsconcordanceforbroken.py . It's showing 165 ports ATM, a few with PRs to fix them. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Configuring 'RUN_DEPENDS'
On Tue, Mar 03, 2009 at 07:29:36AM -0500, Jerry wrote: A port I am creating has a RUN_DEPENDS of either 'curl' or 'wget'. I have tried several times to write some sort of test in the make file to determine if one or the other were installed, and if neither then to install 'curl'. I suppose I could create an OPTIONS to install one or the other; however, I have not gotten that to work correctly either. I looked at Postfix's Makefile, and got a few ideas from it; however, not enough to get what I want to work. The port will also require Clamav, either the standard port or the devel one. Therefore I have two run dependencies to adjust. Use the one available or install one if neither is all ready installed. I tried Googling and the Porters Handbook, but I cannot find what I am looking for. Is it possible? I assume it must be. A regular 'if' or 'case' statement I would normally use does not work in a make file. Can you post your Makefile so we can get a better understanding of what you're trying to do. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Configuring 'RUN_DEPENDS'
* Jerry (ges...@yahoo.com) wrote:
A port I am creating has a RUN_DEPENDS of either 'curl' or 'wget'. I
have tried several times to write some sort of test in the make file to
determine if one or the other were installed, and if neither then to
install 'curl'. I suppose I could create an OPTIONS to install one or
the other; however, I have not gotten that to work correctly either.
You'll need something like this:
---
.include bsd.port.pre.mk
.if exists(${LOCALBASE}/bin/wget) !exists(${LOCALBASE}/bin/curl)
RUN_DEPENDS+= wget:${PORTSDIR}/ftp/wget
.else
RUN_DEPENDS+= curl:${PORTSDIR}/ftp/curl
.endif
---
You should be careful though to match this with your program's logic.
I.e. `what does it do if both wget and curl are installed?' The above
case is for `it uses curl then' answer.
The port will also require Clamav, either the standard port or the
devel one. Therefore I have two run dependencies to adjust.
No, you don't. clamav and clamav-devel are conflicting ports that
install the same files, so should you depend on clamav as
RUN_DEPENDS=clamscan:${PORTSDIR}/security/clamav
or
LIB_DEPENDS=clamav:${PORTSDIR}/security/clamav
if clamav-devel is installed instead, dependency will still match it and
it'll be used. Note `clamav', not `clamav.5' in LIB_DEPENDS.
I tried Googling and the Porters Handbook, but I cannot find what I am
looking for. Is it possible? I assume it must be. A regular 'if' or
'case' statement I would normally use does not work in a make file.
From my experience, the best source for digging examples of such
nontrivial cases are Makefiles for other ports. grep'ping portstree
is too slow, so it's better to create an index like that:
find -L /usr/ports -name Makefile -maxdepth 3 -mindepth 3 -exec grep -H '' {}
\; MAKEFILES.INDEX
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Configuring 'RUN_DEPENDS'
On Tue, 3 Mar 2009 09:55:27 -0500 Wesley Shields w...@freebsd.org wrote: Can you post your Makefile so we can get a better understanding of what you're trying to do. The Makefile is available here: http://seibercom.net/logs/Makefile That is what I have so far. As written, it works. However, I do not need both 'wget' and 'curl' to be installed, although it does not make any difference if they are. I want a way to check if either is installed, and if not, then install 'curl'. The reason being that if a user is all ready using 'wget', installing curl is not required. There are two versions of Clamav in the ports system. I have idea how to test to see which is installed and use that one. If neither is installed, then I would want to install the 'stable' version. I cannot find anything in the Porters Handbook that covers this. -- Jerry ges...@yahoo.com Money will say more in one moment than the most eloquent lover can in years. signature.asc Description: PGP signature
Re: Configuring 'RUN_DEPENDS'
On Tue, 3 Mar 2009 18:37:39 +0300
Dmitry Marakasov amd...@amdmi3.ru wrote:
[snip]
The port will also require Clamav, either the standard port or the
devel one. Therefore I have two run dependencies to adjust.
No, you don't. clamav and clamav-devel are conflicting ports that
install the same files, so should you depend on clamav as
RUN_DEPENDS= clamscan:${PORTSDIR}/security/clamav
or
LIB_DEPENDS= clamav:${PORTSDIR}/security/clamav
OK, I understand what you are saying. However, the script that the port
will install requires a version of Clamav = 0.94.2 to work. Would
prefixing either clamscan or clamav with =0.94.2 work? Unfortunately,
I am not at the computer where the test Makefile, etc. is located to
try it out myself.
--
Jerry
ges...@yahoo.com
Fifty flippant frogs
Walked by on flippered feet
And with their slime they made the time
Unnaturally fleet.
signature.asc
Description: PGP signature
Re: restart a script in etc/rc.d
Oliver Lehmann wrote:
Doug Barton wrote:
Artis Caune wrote:
There is logic error in bacula rc.d script. It should first set
default variables and only then use them.
pidfile=${bacula_fd_pidfile}
: ${bacula_fd_pidfile=/var/run/bacula-fd.9102.pid}
If you don't set pidfile in rc.conf, pidfile is so it kills all
bacula-fd's
Yes, I tried to convince the OP to fix this, but he thought he had it
covered, so I'm giving him the opportunity to prove me wrong. :)
Yeah this did it - Its working now.
I thought you where just telling me that to have another pidfile for the
2nd start script - I missed the point that it was empty for the first one
and because of that it is falling back to ps...
I'll probably write a PR and commit it after aproval for PROVIDE and the
pidfile setting...
Excellent. :)
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 freebsd-ports-unsubscr...@freebsd.org
Re: firefox and anti aliased printouts
Oliver Lehmann lehm...@ans-netz.de wrote: I don't know when this first occured (maybe when switching from firefox 2 to 3) but all the printouts I'm doing from a webpage have their fonts displayed extremly grainy. It is hard to read anything on the printout. Any idea how I can get my firefox to print nice anti aliased fonts? For web pages that want specific fonts, such as Arial, Firefox (or maybe an underlying component, i.e., cairo or fontconfig) ends up picking a bitmapped font. There are several workarounds for this. * Completely disable bitmapped fonts in fontconfig (70-no-bitmaps.conf). I'm told future versions of fontconfig will do this anyay. Right now it has the disadvantage that if you use the default X11 fonts, it kills various non-Western scripts. For instance, no more Japanese in Firefox. * Do what OpenBSD did for its upcoming 4.5 release and gently force fontconfig to map Arial and friends to Bitstream fonts. http://www.openbsd.org/cgi-bin/cvsweb/xenocara/lib/fontconfig/conf.d/31-nonmst.conf?rev=1.2 * Install x11-fonts/liberation-fonts-ttf and write a fontconfig configuration file that maps Arial and friends to their Liberation equivalents. * Install x11-fonts/webfonts to get the original Microsoft fonts if you don't mind being touched by evil. -- Christian naddy Weisgerber na...@mips.inka.de ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Configuring 'RUN_DEPENDS'
* Jerry (ges...@yahoo.com) wrote:
No, you don't. clamav and clamav-devel are conflicting ports that
install the same files, so should you depend on clamav as
RUN_DEPENDS= clamscan:${PORTSDIR}/security/clamav
or
LIB_DEPENDS= clamav:${PORTSDIR}/security/clamav
OK, I understand what you are saying. However, the script that the port
will install requires a version of Clamav = 0.94.2 to work. Would
prefixing either clamscan or clamav with =0.94.2 work? Unfortunately,
I am not at the computer where the test Makefile, etc. is located to
try it out myself.
As far as I understand, that won't work with clamav-devel.
RUN_DEPENDS=clamav=0.94.2:${PORTSDIR}/security/clamav
makes a port depend not on installed file but on specific package,
so clamav-devel will likely not match this rule. I think there's
no need in such strict dependency, as clamav 0.94.2 is in the tree
for 3 months already.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Dead projects in ports tree
On Sat, 28 Feb 2009 17:09:04 -0600, Garrett Cooper yanef...@gmail.com wrote: Just trying to amass cruft in the ports tree that could be marked deprecated and removed. Some assistance in amassing the list would be helpful... multimedia/openquicktime - no movement in CVS / SVN for 1+ years; no releases in the past 3 years I'll continue posting more items to this thread as I find them... Guys, no ports are going to be get remove when they have dead projects or else. If these ports work correct, fetchable and not vulnerability, then there is no reason to remove. Just don't touch these ports, and these ports aren't going to bother and bite you. The BROKEN and pointyhat will tell you when those ports are ready to get remove. Therefore, please use your time on something else to make yourself more useful. Cheers, Mezz Thanks, -Garrett -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Xfce 4.6 - what changes are needed?
Hello, OK, so now Xfce 4.6 is in our ports tree. Great job. But - some things are not working like they used to, and there is no entry in /usr/ports/UPDATING. Are there any documentation elsewhere that describes what changes are needed to get this working again? When I did 'startxfce4' after the upgrade, all my icons in the panel was gone. I had to add them manually. Is that how it should be? Another example, xfce4-mixer claims that my sound card is Unknown (OSS Mixer), is that correct? And the cpugraph plugin crashes (signal 11) when you try to add it to the panel, is somebody working on a fix? -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
SDL / Pulseaudio
Hi list, devel/sdl12 doesn't pick up pulseaudio, no matter if I select it in make config or not. I didn't find the time to dig further, but I noticed 2 bits: - the dependency to libpulse-simple.so.0 isn't set in the Makefile - if I run ./configure without args, it correctly finds the lib and compiles the SDL audio driver for it Is this a known issue or am I missing some other port? Regards, Andre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xfce 4.6 - what changes are needed?
Torfinn Ingolfsen schreef: Hello, OK, so now Xfce 4.6 is in our ports tree. Great job. [...] And the cpugraph plugin crashes (signal 11) when you try to add it to the panel, is somebody working on a fix? I send a bug report [1] for the cpugraph plugin to the upstream authors, but I haven't heard anything yet. The version in the ports tree (0.3.0) is the last version working on BSD, the latest released version (0.4.0) does not support BSD. The authors promised it would be restored in the next release, but I haven't seen it yet. I will invent a local fix for version 0.3.0. [1] http://bugzilla.xfce.org/show_bug.cgi?id=4920 Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xfce 4.6 - what changes are needed?
Torfinn Ingolfsen wrote: Hello, OK, so now Xfce 4.6 is in our ports tree. Great job. But - some things are not working like they used to, and there is no entry in /usr/ports/UPDATING. Are there any documentation elsewhere that describes what changes are needed to get this working again? When I did 'startxfce4' after the upgrade, all my icons in the panel was gone. I had to add them manually. Is that how it should be? Hi, Checkout this thread: http://foo-projects.org/pipermail/xfce4-dev/2009-February/026295.html There are some problems with the icon theme in 4.6 which are known and I'm not sure if they will do anything about it right now. - cjg Another example, xfce4-mixer claims that my sound card is Unknown (OSS Mixer), is that correct? And the cpugraph plugin crashes (signal 11) when you try to add it to the panel, is somebody working on a fix? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Configuring 'RUN_DEPENDS'
On Tue, 3 Mar 2009 20:47:15 +0300
Dmitry Marakasov amd...@amdmi3.ru wrote:
As far as I understand, that won't work with clamav-devel.
RUN_DEPENDS= clamav=0.94.2:${PORTSDIR}/security/clamav
makes a port depend not on installed file but on specific package,
so clamav-devel will likely not match this rule. I think there's
no need in such strict dependency, as clamav 0.94.2 is in the tree
for 3 months already.
I have given up on the idea too. There is probably a way; however, it
is beyond my meager skills. I am just using:
clamav=0.94.2:${PORTSDIR}/security/clamav
It will probably cause a conflict with some users who have the 'devel'
version installed though. In any case, version 95 should be release
shortly. It is all ready at 95RC1 or 2.
I really appreciate all of the help I have been given on this matter.
--
Jerry
ges...@yahoo.com
The worst part of having success is trying
to find someone who is happy for you.
Bette Midler
signature.asc
Description: PGP signature
Re: SDL / Pulseaudio
On, Tue Mar 03, 2009, Andre Heider wrote: Hi list, devel/sdl12 doesn't pick up pulseaudio, no matter if I select it in make config or not. I didn't find the time to dig further, but I noticed 2 bits: - the dependency to libpulse-simple.so.0 isn't set in the Makefile I missed that one, sorry. It will be fixed soon. - if I run ./configure without args, it correctly finds the lib and compiles the SDL audio driver for it Is this a known issue or am I missing some other port? For some weird reason the --enable-pulseaudio switch will disable PulseAudio support in 1.2.13. That'll be fixed as well. Thanks for noticing and notifying :-). Regards Marcus pgp3fNfQy0HCW.pgp Description: PGP signature
Re: SDL / Pulseaudio
On Wed, Mar 4, 2009 at 12:24 AM, Marcus von Appen m...@freebsd.org wrote: On, Tue Mar 03, 2009, Andre Heider wrote: Hi list, devel/sdl12 doesn't pick up pulseaudio, no matter if I select it in make config or not. I didn't find the time to dig further, but I noticed 2 bits: - the dependency to libpulse-simple.so.0 isn't set in the Makefile I missed that one, sorry. It will be fixed soon. - if I run ./configure without args, it correctly finds the lib and compiles the SDL audio driver for it Is this a known issue or am I missing some other port? For some weird reason the --enable-pulseaudio switch will disable PulseAudio support in 1.2.13. That'll be fixed as well. Thanks for noticing and notifying :-). Thank you for the fast answer and the upcoming fixes ;) Regards Marcus ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[PATCH] python25 broken on current
The lang/python25 port fails to build on CURRENT from:
FreeBSD 8.0-CURRENT #0: Sun Mar 1 09:36:35 EET 2009
bu...@kobe:/usr/obj/usr/src/sys/KOBE
Apparently, the `configure.in' script of Python is missing a header file
in one of the custom check programs, which I could work around by
patching its `configure.in' script:
r...@kobe:/usr/ports/lang/python25# more files/patch-configure.in
--- configure.in.orig 2009-03-04 04:01:25.0 +0200
+++ configure.in2009-03-04 04:00:45.0 +0200
@@ -2533,6 +2533,7 @@
#include netdb.h
#include string.h
#include sys/socket.h
+#include arpa/inet.h
#include netinet/in.h
main()
r...@kobe:/usr/ports/lang/python25#
But I don't know enough about Ports to make ports/lang/python25/Makefile
run autoconf on configure.in before trying to `make configure'. I tried
patching the port Makefile with:
r...@kobe:/usr/ports/lang/python25# diff -u Makefile.orig Makefile
--- Makefile.orig 2009-03-04 04:26:51.0 +0200
+++ Makefile2009-03-04 04:25:17.0 +0200
@@ -26,6 +26,9 @@
INSTALL_TARGET=altinstall
MAN1= ${PYTHON_VERSION}.1
+USE_AUTOTOOLS= autoconf:262:env
+AUTOCONF_ARGS= ${CONFIGURE_SCRIPT}.in
+GNU_CONFIGURE= yes
USE_PYTHON=yes
PYTHON_VERSION=python2.5
PYTHON_NO_DEPENDS= yes
r...@kobe:/usr/ports/lang/python25#
But this doesn't seem to work as I expected.
If I manually invoke `autoconf-2.62' in the WRKSRC directory of the port
and then `make configure' it builds fine.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Configuring 'RUN_DEPENDS'
On Tue, Mar 03, 2009 at 05:38:14PM -0500, Jerry wrote:
On Tue, 3 Mar 2009 20:47:15 +0300
Dmitry Marakasov amd...@amdmi3.ru wrote:
As far as I understand, that won't work with clamav-devel.
RUN_DEPENDS= clamav=0.94.2:${PORTSDIR}/security/clamav
makes a port depend not on installed file but on specific package,
so clamav-devel will likely not match this rule. I think there's
no need in such strict dependency, as clamav 0.94.2 is in the tree
for 3 months already.
I have given up on the idea too. There is probably a way; however, it
is beyond my meager skills. I am just using:
clamav=0.94.2:${PORTSDIR}/security/clamav
It will probably cause a conflict with some users who have the 'devel'
version installed though. In any case, version 95 should be release
shortly. It is all ready at 95RC1 or 2.
If either clamav or clamav-devel will work you can just specify a
dependency on sbin/clamd?
-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [PATCH] python25 broken on current
On Wed, 04 Mar 2009 04:28:24 +0200, Giorgos Keramidas keram...@freebsd.org wrote: The lang/python25 port fails to build on CURRENT from: FreeBSD 8.0-CURRENT #0: Sun Mar 1 09:36:35 EET 2009 bu...@kobe:/usr/obj/usr/src/sys/KOBE Apparently, the `configure.in' script of Python is missing a header file in one of the custom check programs, which I could work around by patching its `configure.in' script: r...@kobe:/usr/ports/lang/python25# more files/patch-configure.in --- configure.in.orig 2009-03-04 04:01:25.0 +0200 +++ configure.in2009-03-04 04:00:45.0 +0200 @@ -2533,6 +2533,7 @@ #include netdb.h #include string.h #include sys/socket.h +#include arpa/inet.h #include netinet/in.h main() r...@kobe:/usr/ports/lang/python25# Nevermind... Sorry for the noise. Apparently, src/sys/sys/cdefs.h changes in the last few days cause most of this (and other issues). ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Configure fails for open-vm-tools
I'm getting this error when trying to build the latest open-vm-tools ports: configure: error: uriparser library not found or is too old. Please configure without Unity (using --disable-unity) or install the liburiparser devel package. I still get the same error after installing the uriparser port. -- To send me a personal email, please place [personal] in the Subject line. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xfce 4.6 - what changes are needed?
Hi Torfinn, Torfinn Ingolfsen wrote: When I did 'startxfce4' after the upgrade, all my icons in the panel was gone. I had to add them manually. Is that how it should be? Unfortunally yes - I told them quite some times before the final release and all the xfce guys told me was use another icon theme. I then made the Tango theme a build dependency and changed the default xml files delivery by xfce4-conf to select this icon theme. When you have already an installation, you have probably still Rodent configured which is gone now. Please call the Settings Manager, Choose Appearance, The icon tab and then select Tango as Icon theme. This will bring you most of the icons back (not all of course...). Another example, xfce4-mixer claims that my sound card is Unknown (OSS Mixer), is that correct? This is correct. And the cpugraph plugin crashes (signal 11) when you try to add it to the panel, is somebody working on a fix? I don't. I hope you've read the text I output on x11-wm/xfce4 installation about configuring PolicyKit as well for having the ability to reboot/shutdown the system from inside xfce4. -- 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 freebsd-ports-unsubscr...@freebsd.org
Re: Xfce 4.6 - what changes are needed?
Oliver Lehmann wrote: Hi Torfinn, Torfinn Ingolfsen wrote: When I did 'startxfce4' after the upgrade, all my icons in the panel was gone. I had to add them manually. Is that how it should be? Unfortunally yes - I told them quite some times before the final release and all the xfce guys told me was use another icon theme. I then made the Tango theme a build dependency and changed the default xml files delivery by xfce4-conf to select this icon theme. When you have already an installation, you have probably still Rodent configured which is gone now. Please call the Settings Manager, Choose Appearance, The icon tab and then select Tango as Icon theme. This will bring you most of the icons back (not all of course...). I'm just wondering - does someone think an entry about this in UPDATING would be good? I can of course add one if wanted. -- 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 freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: ktorrent-3.1.6_1
Does anyone have any ideas of what to look into? I'm about to decide Wine+uTorrent would be an easier route than trying to get ktorrent to work decently. I've tried ktrace again but all I seem to find in it are reads, and a ~1 second ktrace is 4MB. Jonathan Jonathan wrote: Nikolay Tychina wrote: Hello, i installed ktorrent3 and it seems to be very slow while checking pieces. (~2mb per second) (Deluge do it much more faster, i didn't try any other clients though) Do you have the same problem? Same issue here. I get ~4MB/s or so. I started digging around and found that according to gstat (output at end) ktorrent is writing 50-60MB/s to ad18, which is my boot drive, sustained. Most of the other drives in the system are completely idle and belong to the ZFS pool the torrent data is actually on. I've checked using fstat and lsof and nothing leaps out at me. I also watched disk and swap space usage during the check and see nothing changing despite the apparent massive write load. I even tried doing a ktrace + kdump and searching for write but didn't find anything there either. I don't claim to be any expert with any of those tools though. Does anyone have any ideas on what to look at next? Thanks, Jonathan dT: 1.035s w: 1.000s L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 0 0 0 00.0 0 00.00.0| ad8 0 0 0 00.0 0 00.00.0| ad8s1 0 34 0 00.0 32 430.55.1| ad16 0 0 0 00.0 0 00.00.0| ad8s1a 0 0 0 00.0 0 00.00.0| ad8s1c 0 0 0 00.0 0 00.00.0| acd0 1 3684 0 00.0 3684 589210.2 81.8| ad18 1 3684 0 00.0 3684 589210.2 83.2| ad18s1 0 36 0 00.0 34 392.19.2| ad10 0 29 0 00.0 27 331.17.9| ad12 0 34 0 00.0 32 430.45.5| ad14 1 3684 0 00.0 3684 589210.2 85.8| ad18s1a 0 0 0 00.0 0 00.00.0| ad18s1b 0 0 0 00.0 0 00.00.0| ad18s1c 0 34 0 00.0 33 833.06.0| da0 0 0 0 00.0 0 00.00.0| ad20 0 37 0 00.0 36 783.46.9| da1 0 36 0 00.0 35 832.35.9| da2 0 41 0 00.0 40 693.47.6| da3 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
