Thanks, this is the reply that I was looking for. Sorry, wish I would have
found that first, but I didn't know where to look or what phrase to google
after I had already looked for a while.
From: Brandon Allbery
To: Kenneth Miller
Cc: "macports-us...@lists.
Yeah you're right, I guess I should have thought about that. But then again,
there could be a minimal trusted base, but that's a matter for another
argument, my question has been answered.
From: Clemens Lang
To: Kenneth Miller
Cc: macports-dev@lists.macosfo
On Sep 25, 2012, at 14:54, and.dam...@macports.org wrote:
> Revision: 98135
> http://trac.macports.org//changeset/98135
> Author: and.dam...@macports.org
> Date: 2012-09-25 12:54:46 -0700 (Tue, 25 Sep 2012)
> Log Message:
> ---
> port platypus44: removing livecheck since th
On Sep 25, 2012, at 18:36, Mojca Miklavec wrote:
> I would like to try to install Indigo
> (http://ggasoftware.com/opensource/indigo) to be able to draw chemical
> formulas in TeX.
>
> I'm attaching my first attempts to create a Portfile, however I'm stuck with
>ERROR: Framework ApplicationS
Hello,
I would like to try to install Indigo
(http://ggasoftware.com/opensource/indigo) to be able to draw chemical
formulas in TeX.
I'm attaching my first attempts to create a Portfile, however I'm stuck with
ERROR: Framework ApplicationServices not found
in CMake. The build nevertheless sta
On Sep 25, 2012, at 12:21 PM, Andrea D'Amore wrote:
> On Tue, Sep 25, 2012 at 9:04 PM, William Siegrist wrote:
>> There's a duplicate Platypus port.
>
> Nvm, I forgot to correctly set Platypus44's name.
>
> Linting would have shown it.
>
Post-commit linting was broken, but it should be fixe
On Tue, Sep 25, 2012 at 11:05:51AM -0700, Kenneth Miller wrote:
> I feel like this could be a distributed building process for
> everyone-why not have port check a server to see if something has been
> built before (in a similar environment) prior to trying to build
> locally?
Are you suggesting M
On Sep 25, 2012, at 12:14 PM, Andrea D'Amore wrote:
> On Tue, Sep 25, 2012 at 9:04 PM, William Siegrist wrote:
>> There's a duplicate Platypus port.
>
> Where is this duplicate? Is it the same port from previous commit,
> that is Platypus @4.4 is conflicting with Platypus @4.7 ?
You committed
On Tue, Sep 25, 2012 at 9:04 PM, William Siegrist wrote:
> There's a duplicate Platypus port.
Nvm, I forgot to correctly set Platypus44's name.
Linting would have shown it.
--
Andrea
___
macports-dev mailing list
macports-dev@lists.macosforge.org
htt
On Tue, Sep 25, 2012 at 9:04 PM, William Siegrist wrote:
> There's a duplicate Platypus port.
Where is this duplicate? Is it the same port from previous commit,
that is Platypus @4.4 is conflicting with Platypus @4.7 ?
--
Andrea
___
macports-dev mai
it, from what I can see this happens
> with every new port.
> In this case Platypus44 had just been created from Platypus port.
>
> Can you look into it or provide the log file
> /buildbot/ports-slave/buildports-lion-x86_64/build/logs-20120925-111844
> ?
>
>
> [1] h
On Mon, Sep 24, 2012 at 3:40 AM, Ryan Schmidt wrote:
>
> On Sep 23, 2012, at 12:18, Sean Farley wrote:
>
>> Speaking of which, could we please allow the use of fullscreen on Lion
>> or above *without* using Apple's "fullscreen?" i.e. I don't want a new
>> desktop when emacs goes fullscreen.
>
> Th
On Tue, Sep 25, 2012 at 5:25 PM, Kuba Ober wrote:
> Ok, I presume we can keep the port names and only issue wxWidgets28 when
> 30 becomes stable. So I won't be pushing for any wxWidgets port renaming.
> 1. Some wxWidgets-using projects abandoned support for 2.8.
What projects?
> 2. Even for pro
Hi,
> (b) If you are on a supported platform (currently 10.6 / 10.7 Intel x86 /
> x86-64) using default variants and with default install path, *and* the
> port's license permits binary redistribution, *and* you have not forced
> source only with -s or the appropriate macports.conf configuratio
On 2012-9-26 04:05 , Kenneth Miller wrote:
> Why does macports insist on using only local builds?
It doesn't. If a prebuilt package is available, it will be used. There
are a number of reasons why one might not be.
- Josh
___
macports-dev mailing list
m
Ok, I presume we can keep the port names and only issue wxWidgets28 when
30 becomes stable. So I won't be pushing for any wxWidgets port renaming.
There are two issues, then:
1. Some wxWidgets-using projects abandoned support for 2.8.
2. Even for projects that support both 2.8 and 2.9, like, say
On Fri, Sep 21, 2012 at 3:50 PM, Kuba Ober wrote:
> I'm trying to get wxWidgets and packages that use it running on 64 bit cocoa
> systems. Obviously
> the way forward is to get everything on wxWidgets 2.9, but for some packages
> it may not be
> possible just yet. Here's what I propose:
> - re
On Sep 25, 2012, at 03:24, Wahlstedt Jyrki wrote:
> On 22.9.2012, at 10.32, Ryan Schmidt wrote:
>
>> We could take the approach that we take in some other ports, when versions
>> are so different that other ports will need to be able to choose among them:
>> always use a suffix, and make the p
On Tue, Sep 25, 2012 at 10:24 AM, Wahlstedt Jyrki wrote:
> On 22.9.2012, at 10.32, Ryan Schmidt wrote:
>
>> So under this plan, we would rename wxWidgets to wxWidgets28, we would
>> rename wxWidgets-devel to wxWidgets210 or wxWidgets30, and we'd update all
>> ports' dependencies according to the
On 22.9.2012, at 10.32, Ryan Schmidt wrote:
> We could take the approach that we take in some other ports, when versions
> are so different that other ports will need to be able to choose among them:
> always use a suffix, and make the ports simultaneously installable by
> installing to diffe
20 matches
Mail list logo
