Please don't upgrade just yet. I just discovered I broke reinplace
functionality at the last minute yesterday. Any reinplace pattern
that has a dash in it will fail to work (ex. the one in apr-util).
I've committed a fix, but we need to push out 1.4.42, and
unfortunately the release manager
I've fixed it. I feel really stupid about that error.
We need to push out a 1.4.42 now, but jmpp is idle. Hopefully he'll
see my message.
On May 17, 2007, at 2:32 AM, Boey Maun Suang wrote:
On 17/05/2007, at 16:22, Blair Zajac wrote:
Was there a change recently to the reinplace command?
On May 16, 2007, at 23:57, James Berry wrote:
On May 16, 2007, at 9:44 PM, [EMAIL PROTECTED] wrote:
Revision 25283 Author [EMAIL PROTECTED] Date 2007-05-16 21:44:07
-0700 (Wed, 16 May 2007) Log MessageRemove workdir variable. *
Placement of the work symlink in the portdir is now optional
--On 16 May 2007 17:12:10 -0700 James Berry <[EMAIL PROTECTED]> wrote:
Following discussion with several of you, and more thought, my thinking
is now:
(1) Obfuscate plain text email addresses by using the form:
- tld/domain/username
[EMAIL PROT
MacPorts v1.4.42 has been released for self update, correcting a bug
in v1.4.41.
To install this release you should be able to:
sudo port selfupdate
(it will take an hour or so for it to reach the rsync repository).
James
ChangeLog for this release:
Release 1.4.42 (17-May-2007 ta
On May 17, 2007, at 12:36 AM, Kevin Ballard wrote:
Please don't upgrade just yet. I just discovered I broke reinplace
functionality at the last minute yesterday. Any reinplace pattern
that has a dash in it will fail to work (ex. the one in apr-util).
I've committed a fix, but we need to pu
Thanks Kevin,
Regards,
Blair
Kevin Ballard wrote:
I've fixed it. I feel really stupid about that error.
We need to push out a 1.4.42 now, but jmpp is idle. Hopefully he'll see
my message.
On May 17, 2007, at 2:32 AM, Boey Maun Suang wrote:
On 17/05/2007, at 16:22, Blair Zajac wrote:
Wa
On May 16, 2007, at 22:32, Kevin Ballard wrote:
We'd also have to remove the id keyword from all Portfiles, since
user names are email addresses.
I like the information the Id keyword provides, including the user
who last changed the file. I would prefer to find a way to make
usernames n
On May 17, 2007, at 06:00, Ian Eiloart wrote:
On 16 May 2007 17:12:10 -0700 James Berry wrote:
Following discussion with several of you, and more thought, my
thinking
is now:
(1) Obfuscate plain text email addresses by using the form:
- tld/domain/username
On May 17, 2007, at 09:01, [EMAIL PROTECTED] wrote:
Revision: 25292
http://trac.macosforge.org/projects/macports/changeset/25292
Author: [EMAIL PROTECTED]
Date: 2007-05-17 07:01:08 -0700 (Thu, 17 May 2007)
Log Message:
---
Update to upstream version 0.9.1
Provide varian
On 2007-05-15 15:25:29 -0400, Kevin Ballard wrote:
> BTW, I've already fixed this particular issue in trunk. Port will
> now run svn as the user who owns the WC.
This doesn't work here:
Synchronizing from file:///Users/vinc17/wd/macosx/dports
Password:
It shouldn't ask any password (I have a ssh
On May 16, 2007, at 5:12 PM, James Berry wrote:
Following discussion with several of you, and more thought, my
thinking is now:
(1) Obfuscate plain text email addresses by using the form:
- tld/domain/username
[EMAIL PROTECTED] ==> com/bar/use
On May 17, 2007, at 5:47 PM, Jordan K. Hubbard wrote:
On May 16, 2007, at 5:12 PM, James Berry wrote:
Following discussion with several of you, and more thought, my
thinking is now:
(1) Obfuscate plain text email addresses by using the form:
- tld/domain/username
On May 17, 2007, at 5:59 PM, James Berry wrote:
Sure, I agree in principle that we're heading in a direction that
makes what you suggest possible. And this proposal does cover part
of that: if somebody has a macports.org account, they can just use
the user name portion of their email addre
On May 17, 2007, at 6:16 PM, Jordan K. Hubbard wrote:
On May 17, 2007, at 5:59 PM, James Berry wrote:
Sure, I agree in principle that we're heading in a direction that
makes what you suggest possible. And this proposal does cover part
of that: if somebody has a macports.org account, they
On May 17, 2007, at 10:41 AM, Ryan Schmidt wrote:
On May 17, 2007, at 06:00, Ian Eiloart wrote:
On 16 May 2007 17:12:10 -0700 James Berry wrote:
Following discussion with several of you, and more thought, my
thinking
is now:
(1) Obfuscate plain text email addresses by using the
On May 17, 2007, at 20:16, Jordan K. Hubbard wrote:
we have maintainers that don't have commit access? What's the
point of that?
We have many. We have around 41 maintainers [1] with @macports.org
email addresses (all of these are committers) handling about 1013
ports [2], and another
We have 8 ports maintained by "[EMAIL PROTECTED]". Should that be
changed to "[EMAIL PROTECTED]"?
$ grep [EMAIL PROTECTED] */*/Portfile
devel/premake/Portfile:maintainers [EMAIL PROTECTED]
perl/p5-class-returnvalue/Portfile:maintainers
[EMAIL PROTECTED]
perl/p5-file-flat/Portfile:
James Berry writes:
- `port info` now opens the Portfile and displays up-to-date
information.
This allows information about variants to be displayed (eg.
dependencies).
Also allow `port info` to default to current directory if no
name is provided
(eridius r25255).
Dear MacPorts developers,
I just wanted to make sure I've been opening tickets properly, since
a few have not been getting feedback. That could easily be because you
are busy with other aspects of MacPorts, not to mention the rest of your
lives, but I thought I should just make sure. All
20 matches
Mail list logo
