Re: update
On 03/03/2012, at 10:41 PM, Daniel Ericsson wrote: On 3 mar 2012, at 14:07, James Linder wrote: Error: Target org.macports.activate returned: Image error: /Library/LaunchAgents/org.freedesktop.dbus-session.plist already exists and does not belong to a registered port. Unable to activate port dbus. Use 'port -f activate dbus' to force the activation. As the log says it's not actually gnome-terminal that fails but the activation of one of it's dependencies, 'dbus'. It seems you have a lingering 'org.freedesktop.dbus-session.plist' file from a previous install. I would do as the log suggests and force the activation with 'port -f activate dbus'. If you moved your /opt/local this is not surprising. If you get any more errors, try to see if they are of the same variety, ie. a file already present but outside of /opt/local and it should be safe to force the activation. Hi Daniel I don't understand this, you certainly do, gnome-terminal built sweetly, so thanks lots James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Macports and Qt development
Hi! I would like to know if other Mac/Qt (optionally also Python) developers are having as many problems as I do. MacPorts installs Qt as a normal library, although there is a variant (non default) that will compile it as a OSX framework. That is fine for non developers, but I noticed that not having a framework is a nightmare if I want to debug my Qt apps. Some times I am forced to compile without debug info, other times my screen get full of warnings about missing symbols. In those cases I can debug my code if I filter out all the warnings I get with every debugger step. For some reason, lately I can no longer debug without thousand of warnings a hello world in qt. Something which could be fixed before with DYLD_IMAGE_SUFFIX=_debug Also I use a lot pyside and ipython, which do not compile if Qt was installed as a framework. Therefore it is hard to debug apps with them My solution so far is installing the official Qt binaries which are compiled as a framework. Since that is the official default, I suppose that is the reason I no longer have problems working with other Qt related tools such as Pyside and iPython gui. So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? cheers, Francisco ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: proftpd
I'll file the ticket and edit the port file as a stopgap measure. I was wondering what i would need to change. Thanks -dan On Sat, Mar 3, 2012 at 10:01 PM, Daniel Ericsson de...@macports.org wrote: On 4 mar 2012, at 02:07, M. Daniel Becque wrote: Does anyone know if sftp is included in the proftpd build? It's not by default and there is no variant to turn it on either. You can submit a ticket with a request for enhancement of the port to allow for this at: https://trac.macports.org/newticket Meanwhile, if you feel confident in following the purftpd documentation on configuring SFTP, you can enable the SFTP module by changing the previously mentioned line 35 in the proftpd Portfile, to read: set modules mod_tls mod_sftp mod_sftp_pam instead of set modules mod_tls remember that any update to proftpd will likely break SFTP for you and you're going to have to, again, manually edit the Portfile and force a reinstall until there is a way to get it compiled from the supplied Portfile. As an aside the proftpd port could probably be enhanced to build most, if not all, modules as DSOs so they're available to turn on, and off, via configuration in proftpd.conf. -- Daniel ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports and Qt development
On 4 mar 2012, at 14:46, Francisco García wrote: So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? This is my own opinion. If you're a developer relying on a framework, you depend on that framework in a wholly different way than a user of an application that has been developed against that framework, exactly as you describe with your debugging woes. If you've had success with the official distribution I'd say go with that. If it's compiled as a framework there isn't any reason it can't integrate with most things built in Macports, with just a little, or even no configuration. It's still useful to know your experience as a developer in using Qt installed from Macports as it can inform others. It would also be useful to know what version of OS X you are on, and which version of Xcode you use, if you do. By using the official Qt distribution you can also follow official documentation and know that it's valid for your situation. A quick search tells me that even with an installation of the official Qt distribution, debugging isn't always painless to get working: http://qt-project.org/wiki/Mac_OS_X_Troubleshooting http://qt-project.org/doc/qt-4.7/debug.html#id-648ce576-8473-4375-80b9-0dad5c38b6ef hope that helps, -- Daniel ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
WordNet environment variables
Dear all, Having installed WordNet using sudo port install wordnet, I'm trying to learn to use it. The man page accessed by entering man wn at the Terminal refers to the WNHOME and WNSEARCHDIR environment variables. However, neither echo $WNHOME nor echo $WNSEARCHDIR yields any result. Please could you tell me whether that's intentional; and if it isn't, how best to fix it (and whether I ought to file a bug report)? Many thanks, Sam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: WordNet environment variables
On 4 March 2012 15:43, Daniel Ericsson de...@macports.org wrote: On 4 mar 2012, at 16:24, Sam Kuper wrote: Having installed WordNet using sudo port install wordnet, I'm trying to learn to use it. This is how I use it from the command-line: $ wn ashes -over Yes, that's what I've been doing so far, but I also wanted to understand the sense index (http://wordnet.princeton.edu/wordnet/man/senseidx.5WN.html) a bit better, and to be able to use other libraries to access WordNet. The man page accessed by entering man wn at the Terminal refers to the WNHOME and WNSEARCHDIR environment variables. However, neither echo $WNHOME nor echo $WNSEARCHDIR yields any result. You shouldn't need to set those (I didn't), but if you do: WNHOME=/opt/local/share/WordNet-3.0 WNSEARCHDIR=/opt/local/share/WordNet-3.0/dict I appreciate that the wn command works without these being set, but other libraries do seem to expect them to be set, so thank you for confirming what they should be. In any case, shouldn't MacPorts set them automatically (and, presumably, also unset them if MacPorts is later used to uninstall WordNet)? Sam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ssh-copy-id in openssh-Portfile-variant-ssh-copy-id.patch
On 2012-03-04 07:22, Ryan Schmidt wrote: On Mar 3, 2012, at 20:06, lllact...@gmx.net wrote: Removing the /usr/bin/ssh-copy-id defaults which ssh-copy-id to /usr/local/bin/ssh-copy-id. Do not remove files in /usr/bin; they were provided by Apple and may be essential to the proper functioning of OS X. In this case, the file /usr/bin/ssh-copy-id is not shipped with OS X, so Dreiel must have placed it there manually. You should not modify or install arbitrary files in /usr as it is controlled by Apple. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
upgrade Xcode to 4.3 with MacPorts 2.0.4
At the MacPorts ProblemHotlist it says that when you upgrade Xcode to 4.3 (and while using MacPorts 2.0.4), then command xcode-select -print-path should give output /Applications/Xcode.app/Contents/Developer. And if you don't see that output -- which was the case on my system -- you should then run: sudo xcode-select -switch /Applications/Xcode.app Is that the correct parameter for xcode-select? After running that, now from xcode-select -print-path I get, of course, just /Applications/Xcode.app. -- Murray Eisenberg murrayeisenb...@gmail.com 80 Fearing Streetphone 413 549-1020 (H) Amherst, MA 01002-1912 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ssh-copy-id in openssh-Portfile-variant-ssh-copy-id.patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2012 17:41, Rainer Müller wrote: On 2012-03-04 07:22, Ryan Schmidt wrote: On Mar 3, 2012, at 20:06, lllact...@gmx.net wrote: Removing the /usr/bin/ssh-copy-id defaults which ssh-copy-id to /usr/local/bin/ssh-copy-id. Do not remove files in /usr/bin; they were provided by Apple and may be essential to the proper functioning of OS X. In this case, the file /usr/bin/ssh-copy-id is not shipped with OS X, so Dreiel must have placed it there manually. You should not modify or install arbitrary files in /usr as it is controlled by Apple. I believe it was shipped with the OS: it's in my /usr/bin/ directory which is untouched by anybody besides Apple (*). OpenSSH OpenSSL were last updated by Software Update the compile time stamp on the above ssh-copy-id is Feb 2011. I suppose I could dig out the package receipt from the relevant Software Update if it is needed. I did read the SSH man page when looking for ssh-copy-id but didn't find it the reason being is it has its own man page `man 1 ssh-copy-id` but not on OS X (BSD). It's present in Linux. Cheers, Phil... (*) apart from certain editors such as BBEdit, Interarchy, etc who install their entirely optional command line tools by design into /usr/bin/. However, I think one would be able to trust the likes of Rich Siegal Peter N. Lewis to know what they're doing. - -- But masters, remember that I am an ass. Though it be not written down, yet forget not that I am an ass. Wm. Shakespeare - Much Ado About Nothing -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: §auto-key-locate cert pka ldap hkp://keys.gnupg.net Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPU7vvAAoJEKpMeDHWT5AD3M0IAKFz0QkirZwDwtTnt9NKBwhf Zj9ofOnjMgRaPHJvcJ9fReWG/gM+OF6fpVOmXsc2/Wy43fsOYKpsfXJ2VUabpfWK Bagas/uYv//eqkWEJEFRuiirTylzs8DwTKIr78ddLQwxAhJO4eYMG5UC91rbMmtl srq0jB/5u75qCca2z3XlyjLrotIwmWOL7Q8DsV4photnV3napgpvoCFLELSOq7wc jXl+JWpMMRi6fV419iJyOH7uYIeVcw6S3TnDxfJRFAIrVEJcuRM0X9Ik8Nyx1v0g E8BmhSw8SJH/l/nDmMrYyL7YNETxiFlvYYLHzFHI2mVEGuO9yOTr1gMeRIcMSSg= =ZGlw -END PGP SIGNATURE- ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: WordNet environment variables
On Sun, Mar 4, 2012 at 11:28, Sam Kuper sam.ku...@uclmail.net wrote: In any case, shouldn't MacPorts set them automatically (and, presumably, also unset them if MacPorts is later used to uninstall WordNet)? That means editing people's shell profiles (which might be ~/.profile or ~/.bash_profile, or potentially others) or possibly ~/.MacOSX/environment.plist on install and again on removal. This is generally not a good idea; there are too many ways for it to go wrong, because it's not designed to be edited that way. (Linux can do it not because the files are different but because the systemwide versions of the files specifically check for additional settings files; OS X doesn't do this and editing Apple's startup files is not a good idea because the worst case failure mode is you run Software Update and thereafter no longer can log in.) -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ssh-copy-id in openssh-Portfile-variant-ssh-copy-id.patch
On Mar 4, 2012, at 2:01 p.m., Phil Dobbin wrote: On 04/03/2012 17:41, Rainer Müller wrote: On 2012-03-04 07:22, Ryan Schmidt wrote: On Mar 3, 2012, at 20:06, lllact...@gmx.net wrote: Removing the /usr/bin/ssh-copy-id defaults which ssh-copy-id to /usr/local/bin/ssh-copy-id. Do not remove files in /usr/bin; they were provided by Apple and may be essential to the proper functioning of OS X. In this case, the file /usr/bin/ssh-copy-id is not shipped with OS X, so Dreiel must have placed it there manually. You should not modify or install arbitrary files in /usr as it is controlled by Apple. I believe it was shipped with the OS: it's in my /usr/bin/ directory which is untouched by anybody besides Apple (*). For what it's worth, my 10.7.3 system does not have /usr/bin/ssh-copy-id. vq ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ssh-copy-id in openssh-Portfile-variant-ssh-copy-id.patch
On Mar 3, 2012, at 21:30, Lawrence Vel�zquez wrote: This is Github's 404 page. The port tried to download a file that's been moved or deleted. The port did nothing; Dreiel downloaded this 404 page manually, as shown earlier: On Mar 2, 2012, at 14:00, lllact...@gmx.net wrote: |$ sudo bash -c cvs -d anon...@anoncvs.mindrot.org:/cvs \ get -p openssh/contrib/ssh-copy-id /usr/local/bin/ssh-copy-id $ sudo chmod +x /usr/local/bin/ssh-copy-id| Right, I tried that first. After that I tried with MacPorts, because I could not find ssh-copy-idin MacPorts at first. So now I know where the 'wrong' html comes from. I will restore the default under /usr/bin to Apple standards (no ssh-copy-id) and follow the MacPorts method in /opt/local/bin/ssh-copy-id. Thanks Phil for the tip: This should help you out with that question: http://oreilly.com/pub/h/66 :-) Dreiel ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: upgrade Xcode to 4.3 with MacPorts 2.0.4
On Mar 4, 2012, at 1:06 p.m., Murray Eisenberg wrote: At the MacPorts ProblemHotlist it says that when you upgrade Xcode to 4.3 (and while using MacPorts 2.0.4), then command xcode-select -print-path should give output /Applications/Xcode.app/Contents/Developer. And if you don't see that output -- which was the case on my system -- you should then run: sudo xcode-select -switch /Applications/Xcode.app Is that the correct parameter for xcode-select? After running that, now from xcode-select -print-path I get, of course, just /Applications/Xcode.app. When I upgraded to Xcode 4.3 and MacPorts 2.0.4, those instructions worked fine. What version of xcode-select do you have? $ xcode-select -version xcode-select version 2307. vq ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Xcode 4.3: Apparently Persistent License Agreement
[Anthony Michael Agelastos iqgra...@gmail.com (2012-02-18 16:22:05 UTC)] On Feb 18, 2012, at 5:45 AM, Aljaž Srebrnič wrote: unfortunately this doesn't work, probably because the license agreement is stored in the home directory of the user (which is /var/empty for macports user) For situations such as this, could/should a $HOME be created for macports user within /opt/local, e.g. /opt/local/home? I am not familiar with how MacPorts handles its builds behind the scenes, but all of the files within /opt/local are owned by root user and admin or wheel groups. So, does macports user do a chown on the data, or is root (through sudo typically) the one doing the building? If root is doing the building, should root be the one with the license agreement? Also, from what I can tell, and I could easily be wrong, this license agreement verification is stored within $HOME/Library/Preferences/com.apple.dt.Xcode.plist. I notice that with the upgrade to macports 2.0.4, there is now a proper home for the macports user. But still, I am getting the dreaded error message. Worse, I seem to be unable to to get rid of it. I have tried sudo -u macports xcodebuild (as root), it does ask me to accept the license agreement, and I do, but nothing changes in ~macports/Library/Preferences/ (which remains empty). I tried adding the -H flag to no avail. So what is the trick required to have the macports user accept the XCode license agreement? - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: upgrade Xcode to 4.3 with MacPorts 2.0.4
xcode-select -version gives xcode-select version 2003. Is that the trouble: I still have the Xcode command-line utilities left from Xcode 4.2? And if so, how to get rid of them (so that I can replace them with the current versions)? The Xcode preferences panel for Components allows one to install the Command Line Tools, but no apparent way to uninstall them. On 3/4/12 3:29 PM, Lawrence Velázquez wrote: On Mar 4, 2012, at 1:06 p.m., Murray Eisenberg wrote: At the MacPorts ProblemHotlist it says that when you upgrade Xcode to 4.3 (and while using MacPorts 2.0.4), then command xcode-select -print-path should give output /Applications/Xcode.app/Contents/Developer. And if you don't see that output -- which was the case on my system -- you should then run: sudo xcode-select -switch /Applications/Xcode.app Is that the correct parameter for xcode-select? After running that, now from xcode-select -print-path I get, of course, just /Applications/Xcode.app. When I upgraded to Xcode 4.3 and MacPorts 2.0.4, those instructions worked fine. What version of xcode-select do you have? $ xcode-select -version xcode-select version 2307. vq -- Murray Eisenberg mur...@math.umass.edu Mathematics Statistics Dept. Lederle Graduate Research Tower phone 413 549-1020 (H) University of Massachusetts413 545-2859 (W) 710 North Pleasant Streetfax 413 545-1801 Amherst, MA 01003-9305 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: upgrade Xcode to 4.3 with MacPorts 2.0.4
[Murray Eisenberg murrayeisenb...@gmail.com (2012-03-04 21:00:20 UTC)] xcode-select -version gives xcode-select version 2003. Is that the trouble: I still have the Xcode command-line utilities left from Xcode 4.2? Could be. Make sure you're running /usr/bin/xcode-select. Maybe you are running one inside /Developer instead. (I have deleted my own /Developer, so I can't know if this is likely. Just guessing.) - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Xcode 4.3: Apparently Persistent License Agreement
On 2012-03-04 21:43 , Harald Hanche-Olsen wrote: I notice that with the upgrade to macports 2.0.4, there is now a proper home for the macports user. But still, I am getting the dreaded error message. Worse, I seem to be unable to to get rid of it. I have tried sudo -u macports xcodebuild (as root), it does ask me to accept the license agreement, and I do, but nothing changes in ~macports/Library/Preferences/ (which remains empty). I tried adding the -H flag to no avail. So what is the trick required to have the macports user accept the XCode license agreement? MacPorts 2.0.4 just copies the agreement to the license from the home directory of the user executing the command. There should not be anything special required once you accepted the license (either by running Xcode.app or xcodebuild), which is stored in ~/Library/Preferences/com.apple.dt.Xcode.plist. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: upgrade Xcode to 4.3 with MacPorts 2.0.4
On 2012-03-04 22:00 , Murray Eisenberg wrote: xcode-select -version gives xcode-select version 2003. Is that the trouble: I still have the Xcode command-line utilities left from Xcode 4.2? And if so, how to get rid of them (so that I can replace them with the current versions)? Apparently, the new version of /usr/bin/xcode-select comes with the Mac OS X 10.7.3 update. Unfortunately, if you first install Mac OS X 10.7.3 and after that install Xcode 4.2, you get the old version. The solution would be to install the 10.7.3 update once again in order to get the new version of xcode-select. Here is the download: http://support.apple.com/kb/DL1484 I am going to add this to the ProblemHotlist. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: upgrade Xcode to 4.3 with MacPorts 2.0.4
From https://developer.apple.com/downloads/index.action I just downloaded and installed Command Line Tools for Xcode - February 2012. Still, running xcode-select -version gives xcode-select version 2003. I do not have any /Developer directory remaining from the older Xcode; I believe it was removed when I chose to uninstall Xcode 4.2.x when installing Xcode 4.3. On 3/4/12 4:09 PM, Harald Hanche-Olsen wrote: [Murray Eisenbergmurrayeisenb...@gmail.com (2012-03-04 21:00:20 UTC)] xcode-select -version gives xcode-select version 2003. Is that the trouble: I still have the Xcode command-line utilities left from Xcode 4.2? Could be. Make sure you're running /usr/bin/xcode-select. Maybe you are running one inside /Developer instead. (I have deleted my own /Developer, so I can't know if this is likely. Just guessing.) - Harald -- Murray Eisenberg mur...@math.umass.edu Mathematics Statistics Dept. Lederle Graduate Research Tower phone 413 549-1020 (H) University of Massachusetts413 545-2859 (W) 710 North Pleasant Streetfax 413 545-1801 Amherst, MA 01003-9305 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Xcode 4.3: Apparently Persistent License Agreement
[Rainer Müller rai...@macports.org (2012-03-04 21:19:54 UTC)] On 2012-03-04 21:43 , Harald Hanche-Olsen wrote: So what is the trick required to have the macports user accept the XCode license agreement? MacPorts 2.0.4 just copies the agreement to the license from the home directory of the user executing the command. Oh. But that would be the root user, then? I don't think the root user has accepted the license, either. There should not be anything special required once you accepted the license (either by running Xcode.app or xcodebuild), which is stored in ~/Library/Preferences/com.apple.dt.Xcode.plist. But most people run macports as root (using sudo), don't they? How exactly does it determine where to copy the accepted license from? - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: upgrade Xcode to 4.3 with MacPorts 2.0.4
On 2012-03-04 22:25 , Rainer Müller wrote: Apparently, the new version of /usr/bin/xcode-select comes with the Mac OS X 10.7.3 update. Unfortunately, if you first install Mac OS X 10.7.3 and after that install Xcode 4.2, you get the old version. The solution would be to install the 10.7.3 update once again in order to get the new version of xcode-select. Here is the download: http://support.apple.com/kb/DL1484 Actually, on a second thought it should be enough to use the full path for xcode-select to make it work more quickly: sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer However, I would recommend you reinstall 10.7.3 just to be sure nothing else was changed in a similar way. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Xcode 4.3: Apparently Persistent License Agreement
[Harald Hanche-Olsen han...@math.ntnu.no (2012-03-04 21:30:49 UTC)] How exactly does it determine where to copy the accepted license from? I got it; by examining $HOME, which is not changed by sudo. My problem is in the way I run my macports upgrades: I run sudo es (es is my login shell of choice), and I run the port command in the shell. Now es (even if not a login shell) sets HOME to the home directory of the owner of the process, in this case /var/root. By manually changing HOME to be my own home directory, I managed to get it to work. - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: py27-game; installation looks clean, but library not found
I'm stuck setting up the new build environment. I need scikits.samplerate, but MacPorts doesn't list that package. I can install it using pip, but I can't figure out how to force it to install in the proper place. BTW, is /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages the correct place for it? On Mar 2, 2012, at 10:53 PM, Brandon Allbery wrote: So how do I proceed from here? Do I have any option other than trying to recreate my current build environment in /opt/local? That's pretty much it; anything else will result in at best inconsistency and at worst stuff failing to run because it's mixing up dylibs from incompatible installs. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Xcode 4.3: Apparently Persistent License Agreement
[Harald Hanche-Olsen han...@math.ntnu.no (2012-03-04 21:38:46 UTC)] [Harald Hanche-Olsen han...@math.ntnu.no (2012-03-04 21:30:49 UTC)] How exactly does it determine where to copy the accepted license from? I got it; by examining $HOME, which is not changed by sudo. So here is a suggestion for making it more robust: If no license agreement is found in $HOME/Library/Preferences, look instead in ~$SUDO_USER/Library/Preferences (probably not valid syntax, but I trust the intent is clear). - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: WordNet environment variables
On Mar 4, 2012, at 14:12, Brandon Allbery wrote: On Sun, Mar 4, 2012 at 11:28, Sam Kuper wrote: In any case, shouldn't MacPorts set them automatically (and, presumably, also unset them if MacPorts is later used to uninstall WordNet)? That means editing people's shell profiles (which might be ~/.profile or ~/.bash_profile, or potentially others) or possibly ~/.MacOSX/environment.plist on install and again on removal. This is generally not a good idea; there are too many ways for it to go wrong, because it's not designed to be edited that way. (Linux can do it not because the files are different but because the systemwide versions of the files specifically check for additional settings files; OS X doesn't do this and editing Apple's startup files is not a good idea because the worst case failure mode is you run Software Update and thereafter no longer can log in.) Right. MacPorts ports don't edit your environment. If you need environment variables set, edit your ~/.profile or ~/.bash_profile or wherever you typically do that and do it there manually. MacPorts itself does a one-time modification to your profile to edit the PATH, so that you can more easily run MacPorts and the software it installs. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: py27-game; installation looks clean, but library not found
On Mar 4, 2012, at 4:44 p.m., Lynn Oliver wrote: I'm stuck setting up the new build environment. I need scikits.samplerate, but MacPorts doesn't list that package. I can install it using pip, but I can't figure out how to force it to install in the proper place. Are you using MacPorts' pip? BTW, is /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages the correct place for it? Yup. You shouldn't have to worry about this. If you are using one of MacPorts' pip ports, things will be installed in the right place. $ port search --name --regex 'pip$' Last time I checked, the ports appended version numbers to the executable. So you'd be running pip-2.7 or something similar. vq ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Scheduled downtime on Mar 5, 16-17 UTC
Hello, there will be a scheduled downtime for the MacPorts Trac and Subversion server due to maintenance at our hosting provider MacOSforge. The services mentioned above will be affected on Monday, March 5th, from 16:00 to 17:00 UTC. Hopefully the interruption will not even take the full time. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: WordNet environment variables
On 4 March 2012 21:58, Ryan Schmidt ryandes...@macports.org wrote: On Mar 4, 2012, at 14:12, Brandon Allbery wrote: On Sun, Mar 4, 2012 at 11:28, Sam Kuper wrote: In any case, shouldn't MacPorts set them automatically (and, presumably, also unset them if MacPorts is later used to uninstall WordNet)? That means editing people's shell profiles (which might be ~/.profile or ~/.bash_profile, or potentially others) or possibly ~/.MacOSX/environment.plist on install and again on removal. This is generally not a good idea; there are too many ways for it to go wrong, because it's not designed to be edited that way. (Linux can do it not because the files are different but because the systemwide versions of the files specifically check for additional settings files; OS X doesn't do this and editing Apple's startup files is not a good idea because the worst case failure mode is you run Software Update and thereafter no longer can log in.) Right. MacPorts ports don't edit your environment. If you need environment variables set, edit your ~/.profile or ~/.bash_profile or wherever you typically do that and do it there manually. Ah, OK; thank you. MacPorts itself does a one-time modification to your profile to edit the PATH, so that you can more easily run MacPorts and the software it installs. I knew about this modification, which is why I was surprised that the WordNet environment variables weren't also set by MacPorts; but I hadn't realised that this was the only modification of this kind that MacPorts makes. Thanks, folks Sam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports and Qt development
On 04/03/2012, at 11:00 PM, macports-users-requ...@lists.macosforge.org wrote: Hi! I would like to know if other Mac/Qt (optionally also Python) developers are having as many problems as I do. MacPorts installs Qt as a normal library, although there is a variant (non default) that will compile it as a OSX framework. That is fine for non developers, but I noticed that not having a framework is a nightmare if I want to debug my Qt apps. Some times I am forced to compile without debug info, other times my screen get full of warnings about missing symbols. In those cases I can debug my code if I filter out all the warnings I get with every debugger step. For some reason, lately I can no longer debug without thousand of warnings a hello world in qt. Something which could be fixed before with DYLD_IMAGE_SUFFIX=_debug Also I use a lot pyside and ipython, which do not compile if Qt was installed as a framework. Therefore it is hard to debug apps with them My solution so far is installing the official Qt binaries which are compiled as a framework. Since that is the official default, I suppose that is the reason I no longer have problems working with other Qt related tools such as Pyside and iPython gui. So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? Your mail implies you'd install Qt via macports. Why would one do that instead of installing the Qt SDK ? All the command line tools are available in the SDK (in fact I do not even know if qtbuilder works, I'm sure it does though.) If you were installing a package that needed Qt would not macports install Qt as needed and transparently? Again, pardon my ignorance, debug with a framework ??? ummm qDebug() and gdb ??? Thanks James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Automatically reinstall ports (UPDATE)
Hi All I just wanted to see if we could bump this reinstall method up to a more stable status. I can and do confirm that under MacPorts 2.0.4, Xcode 4.3 (with persistent License Agreement), and +universal variant enabled…the restore ports TCL script, and steps provided on the Migration Info website https://trac.macports.org/wiki/Migration does work flawlessly. What I did was purposely installed and used some 210 ports (some are dependencies) for a period of about 30 days. During which time, I utilized several areas of development, including a lot of Android related compiles for some rom development, and Android applications, and also a good bit of Security tools development and testing. At some point, I got the feeling that some of my system utilities were not being called when compiling one of the Android roms I help test. During the investigation, I came to the conclusion that possibly my compiler was the problem, so decided to move up to GCC 4.6 (port gcc46), and this is where I encountered some issues with building a port that had once built successfully after being patched (http://trac.macports.org/ticket/33152). Enter my decision to rebuild my entire ports tree. Below are the steps I used from the Migration page: port -qv installed myports.txt port -fp uninstall --follow-dependents installed port clean all curl -O http://svn.macports.org/repository/macports/contrib/restore_ports/restore_ports.tcl chmod +x restore_ports.tcl sudo ./restore_ports.tcl myports.txt Here are the ports and dependencies that were rebuilt successfully using this method: a52dec aalib arm-none-eabi-binutils arm-none-eabi-gcc autoconf automake bison bzip2 cairo cmake cmake cppunit curl curl-ca-bundle cyrus-sasl2 db46 dirac e2fsprogs expat faac findutils flac fontconfig freetype gcc43 gcc_select gdbm gettext ghostscript giflib git-core glib2 glpk gmake gmp gnupg gnupg2 gperf gpg-agent groff gsed help2man icu imlib2 jasper jbig2dec jbigkit jpeg lame lcms lcms2 libassuan libcaca libdca libdv libedit libffi libgcrypt libgpg-error libiconv libid3tag libidn libiptcdata libksba libmad libmng libmodplug libmpc libogg liboil libpaper libpixman libpng libsdl libsdl_gfx libsdl_image libsdl_pango libsdl_sound libsndfile libtheora libtool libusb libusb-compat libvorbis libxml2 lzo2 m4 mpfr mplayer-devel ncurses ncursesw netpbm openjpeg openldap openssl orc ossp-uuid p5.12-class-accessor p5.12-class-data-inheritable p5.12-class-dbi p5.12-class-dbi-uuid p5.12-class-trigger p5.12-clone p5.12-data-uuid p5.12-dbi p5.12-dbix-contextualfetch p5.12-error p5.12-ima-dbi p5.12-io-stringy p5.12-lingua-en-inflect p5.12-locale-gettext p5.12-params-util p5.12-sql-statement p5.12-test-simple p5.12-universal-moniker p5.12-uuid p5.12-version pango pcre perl5 perl5.12 physfs pinentry pkgconfig pngcrush popt psutils pth python27 python_select readline rsync schroedinger schroedinger smpeg speex sqlite3 tcp_wrappers texinfo tiff twolame x264 xorg-bigreqsproto xorg-compositeproto xorg-damageproto xorg-evieproto xorg-fixesproto xorg-fontcacheproto xorg-fontsproto xorg-inputproto xorg-kbproto xorg-libfontenc xorg-libice xorg-libpthread-stubs xorg-libsm xorg-libX11 xorg-libXau xorg-libXaw xorg-libxcb xorg-libXcomposite xorg-libXcursor xorg-libXdamage xorg-libXdmcp xorg-libXevie xorg-libXext xorg-libXfixes xorg-libXfont xorg-libXfontcache xorg-libXi xorg-libXinerama xorg-libxkbfile xorg-libxkbui xorg-libXmu xorg-libXp xorg-libXrandr xorg-libXres xorg-libXScrnSaver xorg-libXt xorg-libXTrap xorg-libXtst xorg-libXv xorg-libXvMC xorg-libXxf86dga xorg-libXxf86misc xorg-libXxf86vm xorg-printproto xorg-randrproto xorg-recordproto xorg-renderproto xorg-resourceproto xorg-scrnsaverproto xorg-trapproto xorg-util-macros xorg-videoproto xorg-xcb-proto xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xf86dgaproto xorg-xf86miscproto xorg-xf86vidmodeproto xorg-xineramaproto xorg-xproto xorg-xtrans xpm xrender XviD xz yasm zlib -- Jeff ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: WordNet environment variables
On Sun, Mar 4, 2012 at 18:43, Sam Kuper sam.ku...@uclmail.net wrote: MacPorts itself does a one-time modification to your profile to edit the PATH, so that you can more easily run MacPorts and the software it installs. I knew about this modification, which is why I was surprised that the WordNet environment variables weren't also set by MacPorts; but I hadn't realised that this was the only modification of this kind that MacPorts makes. Keep in mind that 1) MacPorts would be very difficult to use without that modification, so there's not really much of a way around it; 2) The choice of whether to modify ~/.MacOSX/environment.plist vs. ~/.profile vs. some other mechanism is controlled to some extent by what will be using the WordNet libraries, so it can't really be made for you. (The environment.plist file controls the environment seen by Aqua GUI applications; ~/.profile is seen only in terminals.) Linux actually has a similar divide if you use something like gdm, but solves it at a different level: the system-wide /etc/profile.d directory for per-package environment modifications. Different desktop environments also have different means of injecting environment variables at the same level as OS X's environment.plist, but last time I looked it was different for Gnome and KDE and I don't know if e.g. LXDE has one at all. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: py27-game; installation looks clean, but library not found
Thanks, I didn't even think to look for a MacPorts pip. Another piece of the puzzle fixed. I've gotten far enough along to run parts of my program in the new build environment, and the UI looks quite different. I don't know for sure that the MacPorts install is older than the previous installation, but the GUI is ugly by comparison, so let's hope that's not considered progress. In any case, something is different. In both environments, Tkinter.__version__ returns '$Revision$', so that isn't helpful. Likewise, port contents py27-tkinter shows: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Tkinter-0.0.0-py2.7.egg-info I also use ttk.Notebook, and in both places ttk shows the same version (0.3.1). Can anyone offer any suggestions on how to fix this? On Mar 4, 2012, at 2:31 PM, Lawrence Velázquez wrote: On Mar 4, 2012, at 4:44 p.m., Lynn Oliver wrote: I'm stuck setting up the new build environment. I need scikits.samplerate, but MacPorts doesn't list that package. I can install it using pip, but I can't figure out how to force it to install in the proper place. Are you using MacPorts' pip? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Xcode 4.3: Apparently Persistent License Agreement
[Harald Hanche-Olsen hanche at math.ntnu.no (2012-03-04 21:38:46 UTC)] [Harald Hanche-Olsen hanche at math.ntnu.no (2012-03-04 21:30:49 UTC)] How exactly does it determine where to copy the accepted license from? I got it; by examining $HOME, which is not changed by sudo. So here is a suggestion for making it more robust: If no license agreement is found in $HOME/Library/Preferences, look instead in ~$SUDO_USER/Library/Preferences (probably not valid syntax, but I trust the intent is clear). If you must use a root shell, you can record system-wide license acceptance in /Library/Preferences by running 'xcodebuild -license' as root. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Automatically reinstall ports (UPDATE)
I just wanted to see if we could bump this reinstall method up to a more stable status. I can and do confirm that under MacPorts 2.0.4, Xcode 4.3 (with persistent License Agreement), and +universal variant enabled…the restore ports TCL script, and steps provided on the Migration Info website https://trac.macports.org/wiki/Migration does work flawlessly. It's pretty stable as far as it goes, yes. But it does come with some caveats. Off the top of my head: * It does not handle conflicting ports gracefully at all, it just fails when it comes across them. (You can have conflicting ports installed at the same time, just not active.) * Probably an even bigger one is that it doesn't restore the requested/unrequested status of the ports. This information isn't actually present in the 'port -v installed' output. I think everything ends up marked as requested. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Automatically reinstall ports (UPDATE)
Interesting. Well…the 210 ports listed in my original email all got installed and marked active without issue. The only problems were that 16 core cpu's don't exist yet, and I can't afford a terabyte of DDR3 ram…so the compiling time took all day. -- Jeff On Sun, Mar 4, 2012 at 9:34 PM, Joshua Root j...@macports.org wrote: I just wanted to see if we could bump this reinstall method up to a more stable status. I can and do confirm that under MacPorts 2.0.4, Xcode 4.3 (with persistent License Agreement), and +universal variant enabled…the restore ports TCL script, and steps provided on the Migration Info website https://trac.macports.org/wiki/Migration does work flawlessly. It's pretty stable as far as it goes, yes. But it does come with some caveats. Off the top of my head: * It does not handle conflicting ports gracefully at all, it just fails when it comes across them. (You can have conflicting ports installed at the same time, just not active.) * Probably an even bigger one is that it doesn't restore the requested/unrequested status of the ports. This information isn't actually present in the 'port -v installed' output. I think everything ends up marked as requested. - Josh ___ 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: Macports and Qt development
On Mar 4, 2012, at 09:16, Daniel Ericsson wrote: On 4 mar 2012, at 14:46, Francisco García wrote: So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? This is my own opinion. If you're a developer relying on a framework, you depend on that framework in a wholly different way than a user of an application that has been developed against that framework, exactly as you describe with your debugging woes. If you've had success with the official distribution I'd say go with that. If it's compiled as a framework there isn't any reason it can't integrate with most things built in Macports, with just a little, or even no configuration. It's still useful to know your experience as a developer in using Qt installed from Macports as it can inform others. It would also be useful to know what version of OS X you are on, and which version of Xcode you use, if you do. By using the official Qt distribution you can also follow official documentation and know that it's valid for your situation. A quick search tells me that even with an installation of the official Qt distribution, debugging isn't always painless to get working: http://qt-project.org/wiki/Mac_OS_X_Troubleshooting http://qt-project.org/doc/qt-4.7/debug.html#id-648ce576-8473-4375-80b9-0dad5c38b6ef However, be aware that having the official Qt SDK installed (which will install frameworks in /Library/Frameworks, right?) might cause problems if you then try to install MacPorts ports that use Qt (as would be the case for any other port you install that uses libraries for which you've also installed frameworks in /Library/Frameworks or libraries in /usr/local). ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
