On Jun 11, 2008, at 9:38 AM, Rainer Müller wrote:
...
>
> Have not checked yet if this automatically solves issue #14536 [1].
>
Does this include mercurial (which, as far as I can tell, doesn't
override the port group build style, so should be using setup.py)? If
so, the shebang for hg on my
On Jun 11, 2008, at 3:31 AM, Ryan Schmidt wrote:
The Trac issue tracker is very slow, and it has been for weeks, maybe
months.
View a ticket: 10 seconds
Preview a change to a ticket: 10 seconds
Make a change to a ticket: 14 seconds
Show the New Ticket form: 6 seconds
Show the Custom Query page:
Bill and I will be at the WWDC IT Lab
tomorrow at 11:45am. We invite any MacPorts homies at the show to
come join us for lunch. Email me your cell if you want to connect.
Yours,
Ernie P.
Sent from my iPhone
___
macports-dev mailing list
macports-dev
Rainer Müller wrote:
> Please report back any problems you find.
Answering my own request:
$ pydoc2.5 range
-bash: /opt/local/bin/pydoc2.5:
/opt/local/Library/Frameworks/Python.framework/Versions/2.5/bin/python:
bad interpreter: No such file or directory
$ ls -la
/opt/local/Library/Frameworks
Rainer Müller wrote:
> Ryan Schmidt wrote:
>> MacPorts could check the architectures in each installed Mach-O file
>> to see if it matches the list of architectures requested by the user.
>> If not, a warning could be issued. We may need to be a little
>> selective here and not issue a fatal
Ryan Schmidt wrote:
> Does universal mean "it works at full performance on all
> architectures"? In this case, ports like this that install no
> architecture-specific files should be modified to have an empty
> universal variant selected by default.
>
> Or does universal mean "it has more th
>>> Is there documentation of the mp-specific commands
>>> somewhere, that I overlooked? Things like "system"?
>>> I found the definition in macports/base/src/pextlib1.0/Pextlib.c,
>>> eventually, but it is still a bit uncomfortable. In this case e.g.
>>> I wanted to see if it returns output from s
Ryan Schmidt wrote:
> On Jun 11, 2008, at 03:45, Caspar Florian Ebeling wrote:
>
>> Is there documentation of the mp-specific commands
>> somewhere, that I overlooked? Things like "system"?
>> I found the definition in macports/base/src/pextlib1.0/Pextlib.c,
>> eventually, but it is still a bit un
On Jun 11, 2008, at 03:45, Caspar Florian Ebeling wrote:
> Is there documentation of the mp-specific commands
> somewhere, that I overlooked? Things like "system"?
> I found the definition in macports/base/src/pextlib1.0/Pextlib.c,
> eventually, but it is still a bit uncomfortable. In this case e
The Trac issue tracker is very slow, and it has been for weeks, maybe
months.
View a ticket: 10 seconds
Preview a change to a ticket: 10 seconds
Make a change to a ticket: 14 seconds
Show the New Ticket form: 6 seconds
Show the Custom Query page: 10 seconds
Find all non-closed tickets with "mysq
Is there documentation of the mp-specific commands
somewhere, that I overlooked? Things like "system"?
I found the definition in macports/base/src/pextlib1.0/Pextlib.c,
eventually, but it is still a bit uncomfortable. In this case e.g.
I wanted to see if it returns output from stdout and
exit code.
11 matches
Mail list logo
