On Nov 15, 2012, at 3:42 PM, Craig Treleaven wrote:
> Hi:
>
> Background - MythTV is primarily written in C and C++ but certain functions
> are implemented in Python. Not knowing Python--and more specifically Python
> on OS X and even more specifically, Python on OS X via MacPorts--I am at a
On Thu, Nov 15, 2012 at 5:42 PM, Craig Treleaven wrote:
> Hi:
>
> Background - MythTV is primarily written in C and C++ but certain functions
> are implemented in Python. Not knowing Python--and more specifically Python
> on OS X and even more specifically, Python on OS X via MacPorts--I am at a
Hi:
Background - MythTV is primarily written in C and C++ but certain
functions are implemented in Python. Not knowing Python--and more
specifically Python on OS X and even more specifically, Python on OS
X via MacPorts--I am at a loss as to the proper method to install
Myth's Python binding
On Nov 15, 2012, at 15:47, vincent habchi wrote:
>> You could simplify this by using the [get_canonical_archflags] procedure.
>
> Please feel free to go ahead if you can do it more simply; I just took the
> liberty to alter the portfile because of the ‘opennaintener’ clause.
https://trac.macpo
On Nov 15, 2012, at 05:53, p...@macports.org wrote:
> Revision: 99730
> https://trac.macports.org/changeset/99730
> Author: p...@macports.org
> Date: 2012-11-15 03:53:09 -0800 (Thu, 15 Nov 2012)
> Log Message:
> ---
> New Port: astyle-dev: Development version of astyle (cap
On Nov 15, 2012, at 07:42, p...@macports.org wrote:
> Revision: 99731
> https://trac.macports.org/changeset/99731
> Author: p...@macports.org
> Date: 2012-11-15 05:42:43 -0800 (Thu, 15 Nov 2012)
> Log Message:
> ---
> astyle: added note to conflict with astyle-dev
>
> Modi
On Nov 15, 2012, at 08:21, p...@macports.org wrote:
> Revision: 99734
> https://trac.macports.org/changeset/99734
> Author: p...@macports.org
> Date: 2012-11-15 06:21:31 -0800 (Thu, 15 Nov 2012)
> Log Message:
> ---
> Port astyle-dev: fixed paths
>
> Modified Paths:
>
Ryan,
> It would be better to handle this in Tcl code in the Portfile instead of a
> shell script. The fs-traverse procedure is probably what you want to use.
I definitely agree, but see my previous post (is there a guide available, or,
more precisely, a scroll listing all these magic spells? :
Ryan,
> You could simplify this by using the [get_canonical_archflags] procedure.
Please feel free to go ahead if you can do it more simply; I just took the
liberty to alter the portfile because of the ‘opennaintener’ clause.
BTW, is there any documentation on these arcane functions, besides gu
On Nov 15, 2012, at 14:05, vi...@macports.org wrote:
> Revision: 99744
> https://trac.macports.org/changeset/99744
> Author: vi...@macports.org
> Date: 2012-11-15 12:05:07 -0800 (Thu, 15 Nov 2012)
> Log Message:
> ---
> Patch for universal build (add universal flags to all
On Nov 15, 2012, at 14:01, vi...@macports.org wrote:
> Revision: 99743
> https://trac.macports.org/changeset/99743
> Author: vi...@macports.org
> Date: 2012-11-15 12:01:38 -0800 (Thu, 15 Nov 2012)
> Log Message:
> ---
> Allows universal builds
>
> Modified Paths:
> ---
11 matches
Mail list logo