On Jun 13, 2013, at 11:28, ni...@macports.org wrote:
> Revision: 106995
> https://trac.macports.org/changeset/106995
> Author: ni...@macports.org
> Date: 2013-06-13 09:28:25 -0700 (Thu, 13 Jun 2013)
> Log Message:
> ---
> qtiplot: use qmake portgroup
>
> Modified Paths:
>
On Jun 13, 2013, at 13:56, dev...@macports.org wrote:
> Revision: 106997
> https://trac.macports.org/changeset/106997
> Author: dev...@macports.org
> Date: 2013-06-13 11:56:55 -0700 (Thu, 13 Jun 2013)
> Log Message:
> ---
> transcode: update variants
> * remove +no_x11, add
It looks as though a solution to a problem compiling KDE with Clang
is near. Apparently BSD has now changed over to Clang and found
a similar problem, see https://bugs.kde.org/show_bug.cgi?id=313763
My original report was https://bugs.kde.org/show_bug.cgi?id=300429
KDE compiles and builds OK wit
There are some ports where the package imports modules from setuptools, e.g.
py-protobuf, to do work.
Blair
On Jun 13, 2013, at 10:36 AM, Peter Danecek wrote:
>
> Hi developers,
>
> I just realised, that I have these deactivated py2x-distribute @0.6.45_0 port
> laying a around and I guess
Hi developers,
I just realised, that I have these deactivated py2x-distribute @0.6.45_0 port
laying a around and I guess this basically the issue of this thread.
What I am wondering now: If the dependency can be deactivated, why it is a
dependency in the registry in the first place?
Is py-dis
On Wed, Jun 12, 2013 at 10:18:54PM +, Poor Yorick wrote:
>
> I'm working on breaking the patch up as suggested.
>
Attached is a patch that fixes a couple of problems with the first patch and
uses boolean comparison where it seemed like the thing to do.
--
Yorick
--- macports.tcl20
On Thu, Jun 13, 2013 at 03:14:14PM +0200, Rainer Müller wrote:
>
> In any case, Tcl is not the only dependencies MacPorts currently needs,
> so I don't see a case to do that solely for Tcl. Self-management or
> self-hosting was discussed before but I guess nobody felt a real need to
> actually tak
On Jun 13, 2013, at 8:33 AM, Joshua Root wrote:
> I like omitting unnecessary quoting when the variable is only adjacent
> to whitespace, but when it's up against other characters, having the
> quoting makes it completely clear where the variable name ends. Without
> it, the reader has to know ex
On Thu, Jun 13, 2013 at 08:43:07PM +1000, Joshua Root wrote:
> On 2013-6-13 14:07 , Poor Yorick wrote:
> > Here's another example from the patch. The original version looks like
> > this:
> >
> > if {[catch {eval curl fetch $verboseflag {$source} {$tarpath}} error]} {
> > ...
> >
On 2013-06-13 00:18, Poor Yorick wrote:
> Putting [expr] arguments in braces can result in much better performance as it
> allows Tcl to cache a byte-coded version of the expression. It can also
> avoid unintended processing that might occur via double substitution. Ref
> http://wiki.tcl.tk/102
> Revision: 106983
> https://trac.macports.org/changeset/106983
> Author: larryv at macports.org
> Date: 2013-06-13 00:14:05 -0700 (Thu, 13 Jun 2013)
> Log Message:
> ---
> macports.tcl: Remove unnecessary braces in variable substitutions.
>
> There's already a mix of $foo
On 2013-6-13 14:07 , Poor Yorick wrote:
> Here's another example from the patch. The original version looks like this:
>
> if {[catch {eval curl fetch $verboseflag {$source} {$tarpath}} error]} {
> ...
> }
>
> Taking a look at just the [eval] part:
>
> eval curl
On 2013-6-13 16:29 , David Strubbe wrote:
> Hi all,
>
> I wonder if there is a way in a Portfile to see if a particular port is
> active or not, or alternately, to see if a path dependency was fulfilled
> by the file or the port.
Yes, _portnameactive is exported to the portfile interpreters, and
13 matches
Mail list logo
