Re: [117137] trunk/dports/science

2014-02-17 Thread Ryan Schmidt
It does. So a user affected by that problem will either realize they need to install tk with +x11, or they won’t know what to do and will file a bug report or email me, like someone did today. On Feb 17, 2014, at 09:52, Aljaž 'g5pw' Srebrnič wrote: > I see. I thought the crash happened to all

Re: [117137] trunk/dports/science

2014-02-17 Thread Aljaž 'g5pw' Srebrnič
I see. I thought the crash happened to all the users with magic installed without tk +x11. On 17 febbraio 2014 at 16:26:40, Ryan Schmidt (ryandes...@macports.org) wrote: The reason I didn’t revbump is that this doesn’t change the files installed by the magic ports at all. The only users who wou

Re: [117137] trunk/dports/science

2014-02-17 Thread Ryan Schmidt
The reason I didn’t revbump is that this doesn’t change the files installed by the magic ports at all. The only users who would be affected by the crash at launch are those who have already installed the port but have never tried to launch it; that’s probably not of users, and I’m happy to field

Re: [117137] trunk/dports/science

2014-02-17 Thread Aljaž 'g5pw' Srebrnič
Won’t this require a revbump? On 17 febbraio 2014 at 15:50:46, ryandes...@macports.org (ryandes...@macports.org) wrote: Revision 117137 Author ryandes...@macports.org Date 2014-02-17 06:49:57 -0800 (Mon, 17 Feb 2014) Log Message magic, magic-devel: require +x11 variant of tk to avoid crash on l

Re: How to seamlessly switch from a standard MacPorts install to trunk?

2014-02-17 Thread Joshua Root
On 2014-2-17 18:21 , mk-macpo...@techno.ms wrote: > Hi Josh, > > On 17 Feb 2014, at 07:35 , Joshua Root wrote: >> You don't have to sync your ports tree with svn just because you're >> using the trunk version of base. > Oh, I see! > :) > > That means I misunderstood Clemens’ statement: > > On 1

Re: Wouldn't it be better to make sure a MacPorts installation always stays within /opt/local?

2014-02-17 Thread Rainer Müller
On 2014-02-16 22:23, mk-macpo...@techno.ms wrote: > There is still one big problem with all of this, which is that a ton of > daemons and agents might be running as root or as another user for a given > MacPorts installation. It's not only the daemons running, but also the symlinks in the direct