Hi Randall and James,
Looking at the MacPorts API, I just don't see where the port API
comes into play. I guess I'm just confused.
I don't blame you for being confused. I'm confused every time I
look at that code. It's a ball of worms. The more I know about it
the more I want to rewrite
Hi Randall,
On Nov 26, 2007, at 5:47 PM, Randall Wood wrote:
On 26 Nov 2007, at 09:54, James Berry wrote:
On Nov 26, 2007, at 1:40 AM, Randall Wood wrote:
Is there a good reason not to do this in the MacPorts API?
I'm happy to have any thoughts on the approach. I tend to think
this is in
On 26 Nov 2007, at 09:54, James Berry wrote:
Hi Randall,
On Nov 26, 2007, at 1:40 AM, Randall Wood wrote:
Is there a good reason not to do this in the MacPorts API?
I'm happy to have any thoughts on the approach. I tend to think
this is in the "API" layer, since it's implemented as a tar
Hi Randall,
On Nov 26, 2007, at 1:40 AM, Randall Wood wrote:
Is there a good reason not to do this in the MacPorts API?
I'm happy to have any thoughts on the approach. I tend to think this
is in the "API" layer, since it's implemented as a target. So in other
words, it's on parr with clea
/src/port1.0/portload.tcl
trunk/base/src/port1.0/portunload.tcl
Diff
Modified: trunk/base/src/port/port.tcl (31499 => 31500) --- trunk/
base/src/port/port.tcl 2007-11-26 05:41:11 UTC (rev 31499) +++
trunk/base/src/port/port.tcl 2007-11-26 05:47:26 UTC (rev 31500) @@
-2164,6 +2164,8 @@ livech
On Nov 25, 2007, at 23:47, [EMAIL PROTECTED] wrote:
Revision: 31500
http://trac.macosforge.org/projects/macports/changeset/31500
Author: [EMAIL PROTECTED]
Date: 2007-11-25 21:47:26 -0800 (Sun, 25 Nov 2007)
Log Message:
---
Initial support for port load and port unload ac
