dports/lang/squeak
But every target fails, as I said - not just livecheck. "build" does
the same thing.
- Jordan
On Apr 15, 2007, at 10:57 PM, Paul Guyot wrote:
On Apr 16, 2007, at 2:34 PM, Jordan K. Hubbard wrote:
I'm seeing this from any port and any operation, so it looks like
some
On Apr 16, 2007, at 5:02 PM, Jordan K. Hubbard wrote:
dports/lang/squeak
But every target fails, as I said - not just livecheck. "build"
does the same thing.
Are you running trunk?
Could you please confirm that you have the latest code from trunk or
1.4.1, as well as the latest version
On Apr 15, 2007, at 10:44 PM, [EMAIL PROTECTED] wrote:
Rewrite Pextlib find command. Now actually has useful API. Usage is
find ?-depth? ?-ignoreErrors? target ?target ...? varname body. -
depth identical to -d switch to find. -ignoreErrors causes it to
ignore permission/read errors. Does no
Yes, as I noted in my original message:
> I'm seeing this from any port and any operation, so it looks like
something has gone south in ToT
Sorry, ToT (Top Of Tree) is how we refer to Trunk around here so I'm
more accustomed to using that term.
No local modifications. Confirmed on at lea
On Apr 16, 2007, at 5:17 PM, Jordan K. Hubbard wrote:
Yes, as I noted in my original message:
> I'm seeing this from any port and any operation, so it looks like
something has gone south in ToT
Sorry, ToT (Top Of Tree) is how we refer to Trunk around here so
I'm more accustomed to using
On Apr 16, 2007, at 5:31 PM, Paul Guyot wrote:
diff base/doc/ports.conf /opt/local/etc/ports/ports.conf.in
Of course, I meant:
diff base/doc/ports.conf.in /opt/local/etc/ports/ports.conf
Paul
___
macports-dev mailing list
macports-dev@lists.macosfo
On Apr 15, 2007, at 8:30 PM, Ryan Schmidt wrote:
On Apr 15, 2007, at 10:39, James Berry wrote:
A note for developers working on the MacPorts base code:
- It is your responsibility to keep the ChangeLog up to date with
substantive changes in base.
- Not only does this tell users what has
The users of the original find command was, well, nobody. The few
times I considered using it, I shied away as well. Why? Because I
didn't want to add dependencies on the API when it was, frankly,
pretty bad. It set a global variable (yes, not even local to the
calling procedure, but global
On Apr 16, 2007, at 1:31 AM, Paul Guyot wrote:
Do your boxes run an OS that is supposed to ship in October? I'm
just trying to find a difference between your boxes and those I just
tried to livecheck squeak on. In addition to my development machine,
I successfully livechecked squeak on two
On Apr 16, 2007, at 2:09 AM, Kevin Ballard wrote:
The users of the original find command was, well, nobody. The few
times I considered using it, I shied away as well. Why? Because I
didn't want to add dependencies on the API when it was, frankly,
pretty bad. It set a global variable (yes,
On Apr 16, 2007, at 6:10 PM, Jordan K. Hubbard wrote:
Well, yes, they do. But that should come as no surprise. :)
Well, I have exactly the same diff with the configuration files (the
file:/// url is different, but that's all). I'm out of clues.
The error ("extra characters after close-quot
On Apr 15, 2007, at 1:42 PM, Ryan Schmidt wrote:
Ok, that's what I'm doing (in sleepwatcher), but it's resulting in
weirdness: "port info" shows two "universal" variants; see:
$ port info sleepwatcher | head -n 1
sleepwatcher 2.0.4, Revision 2, sysutils/sleepwatcher (Variants:
universal,
Hi Jordan,
Yes, I cannot tell lie. I did bork eval_variants in r24071. My
change to option parsing suddenly allowed the malformed rsync_options
to begin to be passed into the engine, which then broke. This option
was apparently always silently ignored.
Not long after I discovered this pr
Hmm. And maybe the problem you describe was different than the one I
fixed, in which case I can only say I'm not involved ;)
-jdb
On Apr 16, 2007, at 6:00 AM, James Berry wrote:
Hi Jordan,
Yes, I cannot tell lie. I did bork eval_variants in r24071. My
change to option parsing suddenl
Well, the last couple of deltas to portutil.tcl (can't tell which yet)
appear to have fixed it - it's all working now!
- Jordan
On Apr 16, 2007, at 1:09 AM, Paul Guyot wrote:
On Apr 16, 2007, at 5:02 PM, Jordan K. Hubbard wrote:
dports/lang/squeak
But every target fails, as I said - not
Those ex-opendarwin users who still utilize the opendarwin imap
server should be aware that the opendarwin imap server will be
shutting down sometime following a 10 day warning period from today.
If you still utilize the opendarwin imap server, or if your
@macports.org address forwards to t
On Apr 16, 2007, at 06:21, Paul Guyot wrote:
Ok, that's what I'm doing (in sleepwatcher), but it's resulting in
weirdness: "port info" shows two "universal" variants; see:
$ port info sleepwatcher | head -n 1
sleepwatcher 2.0.4, Revision 2, sysutils/sleepwatcher (Variants:
universal, serve
On Apr 16, 2007, at 4:33 PM, Avi Carmi wrote:
_tgetent referenced from libreadline expected to be defined in /opt/
local/var/db/dports/build/
_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_
dports_devel_ncurses/work/destroot/opt/local/lib/libncurses.5.dylib
Your readlin
On Apr 16, 2007, at 5:35 AM, Jordan K. Hubbard wrote:
On Apr 16, 2007, at 2:09 AM, Kevin Ballard wrote:
I'm also confused as to your complaint about it executing the body
every time. With your original implementation, it executed the
match every time, and every time it succeeded (most of th
Hi Dave,
On Apr 16, 2007, at 2:57 PM, Dave Hill wrote:
In article <[EMAIL PROTECTED]>,
James Berry <[EMAIL PROTECTED]> wrote:
MacPorts 1.4.1 has been released for selfupdate. It should hit the
rsync servers within an hour or so.
If you already have macports installed, simply "sudo port
self
I checked in yesterday a change the search path for ports.conf.
Previously, the first of the following files found was used as the
configuration file for MacPorts:
- File identified by the environment variable PORTSRC
- File at ~/.portsrc
- File at ${prefix}/etc/ports/
On Apr 16, 2007, at 18:41, James Berry wrote:
In other words, if you have a file at ~/.portsrc, you should move
it to ~/.macports/ports.conf.
Why might one use such a file? What might one put in it?
___
macports-dev mailing list
macports-dev@lists
Hi Ryan,
On Apr 16, 2007, at 5:16 PM, Ryan Schmidt wrote:
On Apr 16, 2007, at 18:41, James Berry wrote:
In other words, if you have a file at ~/.portsrc, you should move
it to ~/.macports/ports.conf.
Why might one use such a file? What might one put in it?
The contents are the same as wh
On Apr 16, 2007, at 7:41 PM, James Berry wrote:
Please let me know if you have any comments about this change.
James
More than a comment, a question actually. If I recall and read it
correctly, the previous conf file initialization code in
base/src/darwinports1.0/darwinports.tcl allowe
MacPorts 1.4.2 has been released for selfupdate. It should hit the
rsync servers in an hour or so.
1.4.2 is a minor bug fix release, cut quickly because 1.4.1 didn't
build properly on panther (Mac OS X 10.3.x).
ChangeLog entries:
Release 1.4.2 (16-Apr-2007):
- New logic for variants o
On Apr 16, 2007, at 2:23 PM, Kevin Ballard wrote:
Unlike xinstall/install, find is a command that's far more likely to
be used in the MacPorts base code than in a Portfile. Making it
match the find command-line usage simply makes it more complicated
to use, since it doesn't actually match
On Apr 17, 2007, at 1:24 AM, Jordan K. Hubbard wrote:
find file src {string match *.o $file} {file delete $file}
Except, of course, that what you just typed wouldn't work. It
would find all the object files in the src directory, but not in
any of its subdirectories because it wouldn't matc
27 matches
Mail list logo
