On 2013-8-3 05:47 , Ryan Schmidt wrote:
>
> On Aug 2, 2013, at 13:29, Sterling Smith wrote:
>
>> I'm new to the list. Please gently correct any missteps I make.
>
> Welcome!
>
>> For reasons to remain unnamed, I need to install several python packages for
>> which there are not yet ports. Wh
On 2013-8-3 08:57 , Ryan Schmidt wrote:
>
> On Aug 2, 2013, at 17:41, Sterling Smith wrote:
>
>> When I developed a lone Portfile, port install seemed to try to go off and
>> look for the default python version of the port. For instance, I just
>> submitted https://trac.macports.org/ticket/399
On Fri, Aug 2, 2013 at 8:40 AM, Jim Jagielski wrote:
> I'm thinking it makes sense to break out the subversion port to svn17 and
> svn18, since git-svn only appears to work reliably with subversion 1.7. As
> it is now, git-core +svn "forces" the use of svn 1.8.
I'm assuming this unreliability wit
On Aug 1, 2013, at 13:02, c...@macports.org wrote:
> Revision: 108774
> https://trac.macports.org/changeset/108774
> Author: c...@macports.org
> Date: 2013-08-01 11:02:25 -0700 (Thu, 01 Aug 2013)
> Log Message:
> ---
> new port: port-depgraph, #37721
>
> Added Paths:
> ---
On Aug 2, 2013, at 17:41, Sterling Smith wrote:
> When I developed a lone Portfile, port install seemed to try to go off and
> look for the default python version of the port. For instance, I just
> submitted https://trac.macports.org/ticket/39968 for a py-fortranformat port,
> but when I tri
This doesn't exist yet:
http://trac.macports.org/wiki/SummerOfCode#pip2port
On Aug 2, 2013, at 6:41 PM, Sterling Smith wrote:
> All,
>
> Has anyone considered writing a pypi2port utility (or does one already
> exist)? It seems that one could parse the XML file obtained from [1] to fill
> out
Sean & Ryan,
Thanks for the response.
Sean,
When I developed a lone Portfile, port install seemed to try to go off and look
for the default python version of the port. For instance, I just submitted
https://trac.macports.org/ticket/39968 for a py-fortranformat port, but when I
tried `port
ryandes...@macports.org writes:
> On Aug 2, 2013, at 13:29, Sterling Smith wrote:
>
>> I'm new to the list. Please gently correct any missteps I make.
>
> Welcome!
>
>> For reasons to remain unnamed, I need to install several python packages for
>> which there are not yet ports. While I would
On Aug 2, 2013, at 03:46, light...@macports.org wrote:
> Revision: 108808
> https://trac.macports.org/changeset/108808
> Author: light...@macports.org
> Date: 2013-08-02 01:46:57 -0700 (Fri, 02 Aug 2013)
> Log Message:
> ---
> Updated py-html5lib to latest version 1.0b3 and
On Aug 2, 2013, at 13:29, Sterling Smith wrote:
> I'm new to the list. Please gently correct any missteps I make.
Welcome!
> For reasons to remain unnamed, I need to install several python packages for
> which there are not yet ports. While I would usually do a `pip install
> would like to
MacPorts Developers,
I'm new to the list. Please gently correct any missteps I make.
For reasons to remain unnamed, I need to install several python packages for
which there are not yet ports. While I would usually do a `pip install
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Fri, Aug 2, 2013 at 10:01 AM, Daniel J. Luke wrote:
> On Aug 2, 2013, at 9:40 AM, Jim Jagielski wrote:
> > I'm thinking it makes sense to break out the subversion port to svn17
> and svn18, since git-svn only appears to work reliably with subversion 1.7.
>
> might be easier to just help upstr
On Aug 2, 2013, at 10:03 AM, Jim Jagielski wrote:
>
> I'll take it on, at least until git-svn no longer requires 1.7... Sound OK?
have you checked with upstream about whatever the issue is? (do you have a link
to an upstream bug report on it?)
--
Daniel J. Luke
I'll take it on, at least until git-svn no longer requires 1.7... Sound OK?
On Fri, Aug 2, 2013 at 10:01 AM, Daniel J. Luke wrote:
> On Aug 2, 2013, at 9:40 AM, Jim Jagielski wrote:
> > I'm thinking it makes sense to break out the subversion port to svn17
> and svn18, since git-svn only appear
On Aug 2, 2013, at 9:40 AM, Jim Jagielski wrote:
> I'm thinking it makes sense to break out the subversion port to svn17 and
> svn18, since git-svn only appears to work reliably with subversion 1.7.
might be easier to just help upstream fix git-svn?
> As it is now, git-core +svn "forces" the us
I'm thinking it makes sense to break out the subversion port to svn17 and
svn18, since git-svn only appears to work reliably with subversion 1.7. As
it is now, git-core +svn "forces" the use of svn 1.8.
Comments?
___
macports-dev mailing list
macports-de
On Fri, Aug 2, 2013 at 12:24 AM, Blair Zajac wrote:
>
> Out of curiosity, why do people care about universal builds? So they can
> rsync a build to another platform? Just trying to understand the
> ramifications of this change.
>
>
Up until 2.2.0, I built everything +universal, but only because
I plan to revert this (and bump epoch) tomorrow unless I hear serious
opposition in this ticket:
https://trac.macports.org/ticket/39910
On Jul 29, 2013, at 22:50, m...@macports.org wrote:
> Revision
> 108670
> Author
> m...@macports.org
> Date
> 2013-07-29 22:50:48 -0700 (Mon, 29 Jul 2013)
> Lo
18 matches
Mail list logo
