On 19 mai 2012, at 21:56, Ryan Schmidt wrote:
> Making whitespace changes along with functional changes makes it really hard
> to spot the functional changes. Please make whitespace-only changes in a
> separate commit in the future.
I know that; but in this case, changes were so extensive (one
> +set ports_ignore_older yes
Why? This seems like a really bad idea.
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
On May 18, 2012, at 20:44, Craig Treleaven wrote:
> It would seem to me that MacPorts ought to 'select' the first version of
> python when it is installed, no?
No. The "port select" mechanism is for a user's convenience only. A port may
not rely on the user having selected anything in particul
On May 19, 2012, at 05:37, vi...@macports.org wrote:
> Revision: 93299
> https://trac.macports.org/changeset/93299
> Author: vi...@macports.org
> Date: 2012-05-19 03:37:11 -0700 (Sat, 19 May 2012)
> Log Message:
> ---
> Bump to revision .74. Add gcc47, clang and macports-cl
At 9:47 AM -0400 5/19/12, Jeremy Lavergne wrote:
> Sorry, I'm not following. The first time my port is installing,
it is using depends_lib to pull a bunch of py26-* modules. But the
"port select --set python python26" command hasn't happened so
effectively, there is no python available when
> Sorry, I'm not following. The first time my port is installing, it is using
> depends_lib to pull a bunch of py26-* modules. But the "port select --set
> python python26" command hasn't happened so effectively, there is no python
> available when configure for my port starts running. The so
At 12:27 AM -0400 5/19/12, Jeremy Lavergne wrote:
> So the port I'm working on uses Python and requires a bunch of
modules as dependencies. That's working OK but then my port's
configure _uses_ python to test if the dependencies are installed.
If this is the first time installing python on a
