Re: port command & arguments

2014-04-11 Thread Arno Hautala
On Fri, Apr 11, 2014 at 3:21 AM, René J.V. wrote: > An alias subsitution that replaces a certain argument of a given command > regardless of what order arguments have been passed, and their order? I think this is indeed a feature of ZSH. -- arno s hautala/-| a...@alum.wpi.edu pgp b2c9

Re: MacPorts Self-Update Failure?

2014-04-11 Thread Merton Campbell Crockett
I’m not sure why the MacPorts install scripts failed to complete. I had to power cycle my system to clear the problem as the installer would reject restart and shutdown requests. Anyway, after power cycling the system and downloading and installing yesterday’s Xcode and Command Line Tools upda

Re: gcc 4.8 on MacOS fails depending on -arch order

2014-04-11 Thread Eric Gallager
I am surprised that it even worked at all in the first case; last I heard, FSF GCC did not support multiple `-arch` flags at all... See gcc docs here: http://gcc.gnu.org/onlinedocs/gcc/Darwin-Options.html The code that the Apple version of gcc uses to support multiple arch flags can be found here:

gcc 4.8 on MacOS fails depending on -arch order

2014-04-11 Thread Andrew Jaffe
I am trying to get a recent version of gcc 4.8.2 up on my machine. For a minimal source file, I get errors depending on the order of the -arch flags. (I have used +universal, although in fact some of these same errors occur even without that, strangely) Specifically, `-arch x86_64 -arch i386

Re: port command & arguments

2014-04-11 Thread René J . V . Bertin
On Friday April 11 2014 09:23:25 Ryan Schmidt wrote: > > I’m grateful to René for suggesting possible improvements to MacPorts. Thank you Ryan. That was exactly my intention (suggesting improvements, not your being grateful for it ;)). I'm perfectly able to add aliases to my .tcshrc and/or wri

Re: port command & arguments

2014-04-11 Thread Ryan Schmidt
On Apr 11, 2014, at 05:21, Jan Stary wrote: > Are you even serious? If you can't be bothered > to remember the seven or so command names, > just write yourself some shell wrapper > around calling them something else, > as opposed to imposing needless cruft upon others. I’m grateful to René for s

Re: port command & arguments

2014-04-11 Thread Dominik Reichardt
Please leave irc behaviour at the door. Not to mention that most mail programs provide a filter... > Am 11.04.2014 um 13:14 schrieb René J.V. Bertin : > > Is there an ignore feature on this list, like the one in IRC? > ___ > macports-users mailing list

Re: port command & arguments

2014-04-11 Thread René J . V . Bertin
Is there an ignore feature on this list, like the one in IRC? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port command & arguments

2014-04-11 Thread Jan Stary
> > At this point, one could tell that you conme from linux > > even if you hadn't said so . > > So? What's the point? What if I had suggested reading the table from a plist? "I don't remember the names of these commands. Please change your utility so that it lets me specify a table that replaces

Re: port command & arguments

2014-04-11 Thread Ryan Schmidt
On Apr 11, 2014, at 02:21, René J.V. Bertin wrote: > On Friday April 11 2014 08:09:36 Jan Stary wrote: > >> >> You can easily create aliases in your shell, >> without any need to touch 'port'. > > An alias subsitution that replaces a certain argument of a given command > regardless of what or

Re: dbus obsolete variants?

2014-04-11 Thread René J . V . Bertin
On Thursday April 10 2014 20:52:14 Dominik Reichardt wrote: > (it then eplaced dbus @1.6.12_0+startupitem+universal with dbus > @1.8.0_0+universal) > > Can anyone explain this or tell me whether there needs to be done anything? If port installed dbus tells you you have the +universal version, yo

Re: port command & arguments

2014-04-11 Thread René J . V . Bertin
On Friday April 11 2014 08:09:36 Jan Stary wrote: > > You can easily create aliases in your shell, > without any need to touch 'port'. An alias subsitution that replaces a certain argument of a given command regardless of what order arguments have been passed, and their order? > At this point,