Re: Freeradius 1.1.7 installing problem under Leopard
Andrea, That's fantastic news. Thank you for reviving this port in the vein of the 2.x branch since the 1.x branch is ceasing. Tabitha On 5/21/08, Andrea D'Amore [EMAIL PROTECTED] wrote: On 20/mag/08, at 20:53, Tabitha McNerney wrote: Is anyone in the MacPorts community (besides myself and Jürgen) interested in reviving the FreeRadius MacPort to support the newer major version of the server, 2.x? 2.0.4 has been commited, should be available at next portindex run (every 12 hours). ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Using wxPython
On Wed, 21 May 2008 08:56:12 -0600 Frank Schima [EMAIL PROTECTED] wrote: Indeed the Leopard built-in Python includes pythonw (or the Framework build of python) and works. But I need the MacPorts Python 2.5 to work because I need all the other crunchy goodness that Apple does not provide like scipy, numpy, serial, py25-matplotlib, etc. Are there any wxPython programmers using Python from MacPorts? It's such a shame to have to develop in Linux with VMware to get around this issue. Or worse, switch to GTK :) No need to talk crazy talk! You can get SciPy for Leopard, including NumPy and also matplotlib and wxPython, all with simple pre-built downloads from SciPy and the Python site. See near the bottom of the page at http://www.scipy.org/Download for instructions for installing Python 2.5.2, SciPy and NumPy. I went with the MacPython package option from http://www.pythonmac.org/packages/ There you can also get prebuilt versions of matplotlib and the latest wxPython. They all work well for me. (Well, I haven't used matplotlib, but I don't expect any problems.) I haven't tried PySerial either, but their web site says it works with Mac out of the box, too. Perhaps that's why so little support exists for modern Python from MacPorts: MacPorts doesn't add much to the mix, except confusion. Python supports its own portable build system that works well on Mac OS X. MacPorts is great for compiling C code from projects that don't have Mac support included. Its a real pain compared to downloading a ready-made DNG or package file that installs in seconds with a few clicks. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: git Sources
Is git supported for keeping track of the macports/trunk ? I other words, can I use git in order to get port's source code? Macports in in a SVN repository, but there is a git mirror which gets refreshed regularly, I think. http://github.com/kballard/macports/tree/master Florian -- Florian Ebeling [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Fwd: Help installing gnome with macport
Forwarding because I hit reply instead of reply-all by accident -- Forwarded message -- From: eazy livn [EMAIL PROTECTED] Date: Thu, May 22, 2008 at 9:11 AM Subject: Re: Help installing gnome with macport To: Randall Wood [EMAIL PROTECTED] Thank you Randall for taking time to reply to my request for help. I tried your suggestion. However, the process still fails. I also tried downloading, and installing, the library directly from http://sam.zoy.org/projects/libcaca/ using the library install instructions from that site. Then I tried running the install again, but I continue to receive the same error, which makes me wonder if the checksum being used to validate the file may itself be incorrect. Below is what happens when I tried your suggestion: Thanks again for your help! Best, ~don ip24-254-1-110:/sw/share root# port clean --all libcaca ; --- Cleaning libcaca ip24-254-1-110:/sw/share root# port install libcaca ; --- Fetching libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://sam.zoy.org/projects/libcaca/ --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/downloads/libcaca Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. ip24-254-1-110:/sw/share root# port install gnome; --- Fetching libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://sam.zoy.org/projects/libcaca/ --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/downloads/libcaca Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: gnome-desktop-suite gnome-applets gnome-control-center gnome-settings-daemon gst-plugins-good libcaca libcdio libcddb libdv libshout2 speex taglib wavpack libgnomekbd libxklavier metacity gnome-python-desktop gnome-media gtksourceview gnuregex totem-pl-parser gucharmap system-tools-backends p5-net-dbus p5-xml-twig gnome-audio gnome-backgrounds gnome-games ggz-client-libs libggz guile gmp libsdl_mixer libsdl smpeg py25-gtkglext gtkglext py25-opengl py25-pil py25-setuptools py25-zlib py25-tkinter tcl tk gnome-keyring-manager gnome-mag gnome-session gnome-system-monitor gtkmm cairomm glibmm libsigcxx2 gnome-terminal vte gnome-user-docs gnome-utils gnopernicus libgail-gnome libgtkhtml3 seahorse avahi dbus-python25 gdbm libdaemon py25-gdbm gpgme gnupg bzip2 pth vino yelp firefox-x11 zip zenity Error: Status 1 encountered during processing. An act of kindness, no matter how small, is never wasted. - Aesop --- On Thu, 5/22/08, Randall Wood [EMAIL PROTECTED] wrote: From: Randall Wood [EMAIL PROTECTED] Subject: Re: Help installing gnome with macport To: [EMAIL PROTECTED] Date: Thursday, May 22, 2008, 2:43 AM In this case, it seems that the libcaca source code did not download correctly. Try this: sudo port clean --all libcaca ; sudo port install libcaca If that works, then pick up with building gnome again. On Wed, May 21, 2008 at 2:39 PM, eazy livn [EMAIL PROTECTED] wrote: I'm new to Macports so I request forbearance if my question seems stupid. When I attempt to install gnome I use the following command in a terminal window: 'port install gnome'. After running for a substantial amount of time, I receive the error listed below when the process quits. Thanks for any help anyone can provide. Best, ~don -- Randall Wood [EMAIL PROTECTED] The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy. -- Randall Wood [EMAIL PROTECTED] The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Help installing gnome with macport
Hi Randall, On May 21, 2008, at 12:39 PM, eazy livn wrote: I'm new to Macports so I request forbearance if my question seems stupid. When I attempt to install gnome I use the following command in a terminal window: 'port install gnome'. After running for a substantial amount of time, I receive the error listed below when the process quits. Thanks for any help anyone can provide. Best, ~don --- Fetching libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://sam.zoy.org/projects/libcaca/ --- Verifying checksum(s) for libcaca Error: Checksum (md5) mismatch for libcaca-0.9.tar.bz2 Error: Target org.macports.checksum returned: Unable to verify file checksums Error: The following dependencies failed to build: gnome-desktop- suite gnome-applets gnome-control-center gnome-settings-daemon gst- plugins-good libcaca libcdio libcddb libdv libshout2 speex taglib wavpack libgnomekbd libxklavier metacity gnome-python-desktop gnome- media gtksourceview gnuregex totem-pl-parser gucharmap system-tools- backends p5-net-dbus p5-xml-twig gnome-audio gnome-backgrounds gnome- games ggz-client-libs libggz guile gmp libsdl_mixer libsdl smpeg py25-gtkglext gtkglext py25-opengl py25-pil py25-setuptools py25- zlib py25-tkinter tcl tk gnome-keyring-manager gnome-mag gnome- session gnome-system-monitor gtkmm cairomm glibmm libsigcxx2 gnome- terminal vte gnome-user-docs gnome-utils gnopernicus libgail-gnome libgtkhtml3 seahorse avahi dbus-python25 gdbm libdaemon py25-gdbm gpgme gnupg bzip2 pth vino yelp firefox-x11 zip zenity Error: Status 1 encountered during processing. The libcaca source moved for some reason. I fixed the Portfile to point to the new location. I also wrote up a bug ticket for it. http://trac.macports.org/ticket/15399 In the future, you can write a bug report for problems like this. Please see the wiki page on it: http://guide.macports.org/#project.tickets Cheers! Frank Schima Boulder, CO [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Help installing gnome with macport
On May 22, 2008, at 9:56 AM, Frank Schima wrote: Hi Randall, Heh, i meant Don! Sorry about the name mixup. Cheers! Frank Schima Boulder, CO [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Qt4-mac issue
I have run into a problem using the new version of Qt4-mac (4.4). I am trying to build sqliteman, an application that uses Qt4. It would build fine for me with the prior Qt4 macport version. And I have been informed that it does work fine with 4.4 on other platforms. The problem is that when I try to do the build I get errors from make, after cmake. The problem is that make is looking in the wrong place for include files and such. If I do a verbose build I get things like this on the make: -I/opt/local/include/qt4 -I/opt/local/include/qt4/QtGui But these directories don't exist. I believe that they were the correct place location to find things for Qt4.3? It seems like they were moved to /opt/local/Library/Frameworks So the question is how to get cmake/make to correctly find this change? I am not sure if this is actually a problem with something being cached in my sqliteman directory, or if it is a problem with how cmake locates directories? Is there a bad link somewhere in the Qt install? Frankly I am not sure if this is a bug in Macports Qt4, in sqliteman, in how to use cmake, or where to find the answer. But I figured I would start with macports, since that is where the change in locations for directories occurred. Thanks, --Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Qt4-mac issue
Are you building sqliteman through MacPorts? I just built it myself and it worked fine. When did you install the latest qt4-mac port? If I had to guess, I would bet that you're still running CMake version 2.4.x. I'm running the latest (2.6) and it didn't have any problem building it. Try doing sudo port upgrade cmake and then building sqliteman. Cheers, Tanner Lovelace On Thu, May 22, 2008 at 12:13 PM, Adam Dershowitz [EMAIL PROTECTED] wrote: I have run into a problem using the new version of Qt4-mac (4.4). I am trying to build sqliteman, an application that uses Qt4. It would build fine for me with the prior Qt4 macport version. And I have been informed that it does work fine with 4.4 on other platforms. The problem is that when I try to do the build I get errors from make, after cmake. The problem is that make is looking in the wrong place for include files and such. If I do a verbose build I get things like this on the make: -I/opt/local/include/qt4 -I/opt/local/include/qt4/QtGui But these directories don't exist. I believe that they were the correct place location to find things for Qt4.3? It seems like they were moved to /opt/local/Library/Frameworks So the question is how to get cmake/make to correctly find this change? I am not sure if this is actually a problem with something being cached in my sqliteman directory, or if it is a problem with how cmake locates directories? Is there a bad link somewhere in the Qt install? Frankly I am not sure if this is a bug in Macports Qt4, in sqliteman, in how to use cmake, or where to find the answer. But I figured I would start with macports, since that is where the change in locations for directories occurred. Thanks, --Adam -- Tanner Lovelace http://wtl.wayfarer.org/ (fieldless) In fess two roundels in pale, a billet fesswise and an increscent, all sable. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Qt4-mac issue
I was not building it with macports (it must be a pretty new port, and I had not noticed it before. And I am using 1.1, which is just a beta). I am using cmake 2.6-patch 0. But I did figure out what the problem was. The issue was just that cmake had created a cache in the folder that pointed to the locations of different things. The change in Qt4, to the frameworks locations, was not caught by cmake, so it was using the old set of info. I deleted a few things in the directory that were cmake related. I think that the one that probably did it was deleting CMakeCache.txt. Then doing cmake forced it to find all that stuff again in the new locations. So the lesson is that any applications, that use Qt, but are not in Macports, will be looking in the old locations and won't build properly until they are forced to look in the new place. I would guess that there is something that is functionally like cmake clean that would force this update, but I didn't find that command. --Adam On May 22, 2008, at 9:58 AM, Tanner Lovelace wrote: Are you building sqliteman through MacPorts? I just built it myself and it worked fine. When did you install the latest qt4-mac port? If I had to guess, I would bet that you're still running CMake version 2.4.x. I'm running the latest (2.6) and it didn't have any problem building it. Try doing sudo port upgrade cmake and then building sqliteman. Cheers, Tanner Lovelace On Thu, May 22, 2008 at 12:13 PM, Adam Dershowitz [EMAIL PROTECTED] wrote: I have run into a problem using the new version of Qt4-mac (4.4). I am trying to build sqliteman, an application that uses Qt4. It would build fine for me with the prior Qt4 macport version. And I have been informed that it does work fine with 4.4 on other platforms. The problem is that when I try to do the build I get errors from make, after cmake. The problem is that make is looking in the wrong place for include files and such. If I do a verbose build I get things like this on the make: -I/opt/local/include/qt4 -I/opt/local/include/qt4/QtGui But these directories don't exist. I believe that they were the correct place location to find things for Qt4.3? It seems like they were moved to /opt/local/Library/Frameworks So the question is how to get cmake/make to correctly find this change? I am not sure if this is actually a problem with something being cached in my sqliteman directory, or if it is a problem with how cmake locates directories? Is there a bad link somewhere in the Qt install? Frankly I am not sure if this is a bug in Macports Qt4, in sqliteman, in how to use cmake, or where to find the answer. But I figured I would start with macports, since that is where the change in locations for directories occurred. Thanks, --Adam -- Tanner Lovelace http://wtl.wayfarer.org/ (fieldless) In fess two roundels in pale, a billet fesswise and an increscent, all sable. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Help installing gnome with macport
On May 22, 2008, at 3:01 PM, eazy livn wrote: Hi Frank, Thanks for your efforts. I tried to install the library and still get the same error. I'm wondering if I'm doing something dumb here. Here is the error message: /opt/local eazylivn$ sudo port clean --all libcaca --- Cleaning libcaca /opt/local eazylivn$ sudo port install libcaca --- Fetching libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://sam.zoy.org/projects/libcaca/ --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/libcaca --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch libcaca-0.9.tar.bz2 from http://svn.macports.org/repository/macports/downloads/libcaca Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. Please use reply-all to keep all replies on the list. It takes a little while for the changes to sync I believe. But later today or tomorrow you have to do the following: sudo port selfupdate Then try to install again. sudo port install libcaca sudo port install gnome Cheers! Frank Schima Boulder, CO [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
enabling Variant: options when installing nano
Hello, I am new to macports and I am trying to enable syntax highlighting for nano. I tried just editing the nanorc file but I get errors like this: Error in /opt/local/etc/nanorc on line 3: Command syntax not understood I have read around and I am guessing that I need to set the configuration options when doing the install. I notice that the apps page has a list configuration.args and Variant: options. I can't seem to find any information on how to pass these options to the install. It seems it may be to do with env variables? Rather than particular help configuring nano I would rather have an explanation of how to apply these options as it seems to be not really documented anywhere. I would be very grateful for a nudge in the right direction. max P.s This is my first post to a mailing list so apologies if I have broken any etiquette. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
admin question: can digests be tweaked to come no more often than daily?
Can the threshold for digests be bumped up so we don't get so many per day? I have gotten as many as four digest mailing in a single day, kinda defeats the purpose. Thanks -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: admin question: can digests be tweaked to come no more often than daily?
On May 22, 2008, at 4:03 PM, paul beard wrote: Can the threshold for digests be bumped up so we don't get so many per day? I have gotten as many as four digest mailing in a single day, kinda defeats the purpose. I increased the size threshold for digests. It should be pretty rare now to hit the size threshold before the daily digest is sent. -Bill smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: enabling Variant: options when installing nano
Max Garfinkel wrote: Hello, I am new to macports and I am trying to enable syntax highlighting for nano. I tried just editing the nanorc file but I get errors like this: Error in /opt/local/etc/nanorc on line 3: Command syntax not understood I have read around and I am guessing that I need to set the configuration options when doing the install. I notice that the apps page has a list configuration.args and Variant: options. I can't seem to find any information on how to pass these options to the install. It seems it may be to do with env variables? Rather than particular help configuring nano I would rather have an explanation of how to apply these options as it seems to be not really documented anywhere. I would be very grateful for a nudge in the right direction. I am not a user of nano, but I think you need the +color variant of nano. $ port variants nano [...] color: Enable color syntax highlighting Use the following commands to install nano with this variant: $ sudo port deactivate nano $ sudo port install nano +color P.s This is my first post to a mailing list so apologies if I have broken any etiquette. Welcome as a MacPorts user! No, you didn't do anything wrong :-) Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
enabling syntax highlighting for vim?
A bit like Max, I would like syntax highlighting for vim. I know vim itself is colour capable because the ~ blank line markers and warning messages are in different colours. However, my source code is in boring monochrome. There do not seem to be variants to enable syntax highighting, nor separate packages (or at least, my searches do not reveal them to me). I've even build vim with the +huge variant to no avail. Suggestions? -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ TeX: When you pronounce it correctly to your computer, the terminal may become slightly moist. - D. E. Knuth. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: enabling syntax highlighting for vim?
Cameron Simpson wrote: A bit like Max, I would like syntax highlighting for vim. I know vim itself is colour capable because the ~ blank line markers and warning messages are in different colours. However, my source code is in boring monochrome. There do not seem to be variants to enable syntax highighting, nor separate packages (or at least, my searches do not reveal them to me). I've even build vim with the +huge variant to no avail. There is no variant for it, because basically every vim installation has the ability to do colored syntax highlighting. You just need to configure vim to do it. Also, a google search for vim syntax highlighting revealed a lot of useful answers for me... Anyway, you need the following line in your .vimrc: syntax on See also :help colorscheme how to use other colors instead of the default. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: enabling syntax highlighting for vim?
On 23May2008 03:10, Rainer M?ller [EMAIL PROTECTED] wrote: Cameron Simpson wrote: A bit like Max, I would like syntax highlighting for vim. I know vim itself is colour capable because the ~ blank line markers and warning messages are in different colours. However, my source code is in boring monochrome. [...] There is no variant for it, because basically every vim installation has the ability to do colored syntax highlighting. You just need to configure vim to do it. [...] Anyway, you need the following line in your .vimrc: syntax on I am revealed as a fool. I had believed that because my personal .vimrc was identical on my Mac and on my home machine the deficiency was in vim (I was guessing missing syntax files or missing functionality). But adding the above line to my vimrc turns on syntax colouring and shows I was unwittingly relying on a default setting on other installations (gentoo and fedora linux mostly). Thanks. See also :help colorscheme how to use other colors instead of the default. Ta. I did play with this in the distant past (mostly to try to eliminate the dark blue, close to unreadable on my terminals, which have a black background). I'll revisit this stuff soon. Thanks again, -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ The best way to rob a bank is to own one. - Roberto Calvi ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
missing $CC and $LD settings in some packages
Recent instance: I just rebuilt mercurial using port upgrade. The first attempt failed with a failure I see quite frequently: a command line which commences with -DNDEBUG This is symptomatic of missing the cc/gcc or ld commands, in turn symptomatic of a Makefile using $(CC)/$(LD) and expecting to inherit them from the shell environment. Dodgy but common. My usual workaround is to export CC=gcc and LD=ld and rerun port. And in turn, I had to add: extra_env CC LD to my macports.conf. Is this just an old busted config on my part, or is there a real configuration deficiency here? Cheers, -- Cameron Simpson [EMAIL PROTECTED] DoD#743 http://www.cskk.ezoshosting.com/cs/ We might have been the hundred-millionth or so paying customers at one of the local screenings of Jurassic Park. After all the hoopla, the kid dismissed it as Not bad for a dinosaur movie. And, as if to add insult to injury, she was right. - [EMAIL PROTECTED] (Joe Chew) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: missing $CC and $LD settings in some packages
On May 22, 2008, at 20:59, Cameron Simpson wrote: Recent instance: I just rebuilt mercurial using port upgrade. The first attempt failed with a failure I see quite frequently: a command line which commences with -DNDEBUG This is symptomatic of missing the cc/gcc or ld commands, in turn symptomatic of a Makefile using $(CC)/$ (LD) and expecting to inherit them from the shell environment. Dodgy but common. My usual workaround is to export CC=gcc and LD=ld and rerun port. And in turn, I had to add: extra_env CC LD to my macports.conf. Is this just an old busted config on my part, or is there a real configuration deficiency here? This is a bug which affects Leopard users in some circumstances. A workaround is already in MacPorts base in trunk. You can either build MacPorts trunk from source, or when you encounter the error, simply issue the port upgrade (or port install) command again and it should work the second time. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
