On Oct 3, 2011, at 11:36 PM, Jeremy Lavergne wrote:
> Well there are a couple ways that come to mind:
Ah, ok, I thought there is already a recommended way…
Perhaps I could ask the guys on the KDE-DEVELOP ml? ;-)
___
macports-dev mailing list
macports-dev@
On Oct 3, 2011, at 08:48, ti...@macports.org wrote:
> Revision: 84842
> http://trac.macports.org/changeset/84842
> Author: ti...@macports.org
> Date: 2011-10-03 06:48:48 -0700 (Mon, 03 Oct 2011)
> Log Message:
> ---
> added port soci-devel
> ticket:28939
> Added: trunk/dpo
> How could a shell script detect whether kbuildsyscoa4 had been run after
> install?
Well there are a couple ways that come to mind:
* you can research what kbuildsyscoca4 actually does and look for it (does it
make files, does it set environment stuff, etc)
* you can have your own environmen
On Oct 3, 2011, at 11:24 PM, Jeremy Lavergne wrote:
>> +notes "ATTENION: All users wanting to use skrooge.app should run the
>> command: \n ${prefix}/bin/kbuildsycoca4"
> If I can make a recommendation: I'd make skrooge.app first run a shell script
> checking to see if kbuildsyscoca4 has been ru
> +notes "ATTENION: All users wanting to use skrooge.app should run the
> command: \n ${prefix}/bin/kbuildsycoca4"
If I can make a recommendation: I'd make skrooge.app first run a shell script
checking to see if kbuildsyscoca4 has been run, then proceed to run as usual.
smime.p7s
Description
On Oct 3, 2011, at 11:13 PM, Ryan Schmidt wrote:
> I just dislike the idea that individual ports decide that their messages
> should be displayed more prominently than other ports' messages. If you
> believe the current way that MacPorts displays notes is not visible enough,
> that users will no
On Oct 3, 2011, at 05:29, Marko wrote:
>
> On Oct 3, 2011, at 3:09 AM, Ryan Schmidt wrote:
>> Can we dispense with all the "" formatting? If that's believed to be
>> useful, then it should be MacPorts base that prints it, not each individual
>> port that uses the notes feature. I perso
On Oct 3, 2011, at 09:44, Andrea D'Amore wrote:
> On Mon, Oct 3, 2011 at 03:20, Ryan Schmidt wrote:
>
>>> +use_configure no
>>> +variant universal {}
>
>> I don't have Lion to test this with, but are you sure this works?
>
> Actually I borrowed that from existing nu's portfile.
You can'
Ok, finally I figured out a way to compile AVX instructions. But it is somewhat
crooked. The old ‘as’ assembler in /usr/bin/as must be discarded and replaced
by this script, that uses the clang assembler:
#!/bin/sh
HAS_INPUT_FILE=0
ARGS=$@
while [ $# -ne 0 ]; do
ARG=$1
# Skip opt
On Mon, Oct 3, 2011 at 03:20, Ryan Schmidt wrote:
>> +use_configure no
>> +variant universal {}
> I don't have Lion to test this with, but are you sure this works?
Actually I borrowed that from existing nu's portfile.
I just tested it again: nu2 builds fine boths i386 and x86_64 in Lion.
On 2011-10-3 16:24 , Jordan K. Hubbard wrote:
>
> On Oct 2, 2011, at 6:40 AM, Joshua Root wrote:
>
>> You can certainly change users with su or sudo as part of a shell
>> command you run with system or exec, but the real problem is knowing
>> which user you want to run the command as. There could
On Mon, Oct 3, 2011 at 03:20, Ryan Schmidt wrote:
> I don't have Lion to test this with, but are you sure this works? I only see
> an empty universal variant and no additional code anywhere to actually inform
> nu2 what architectures to build for.
> Here as well I see no mention of what archite
12 matches
Mail list logo
