Dear portfile maintainers,
There was a recent discussion on the list in which it was decided
that we should support obscuring the email addresses in the
maintainer line of our portfiles. If your email address is
[EMAIL PROTECTED], then the obscured address entered into the
portfile would
Please don't do this. Our source files really should be using soft
tabs if possible, so if we are going to do file-wide changes we
should move to that standard.
On Jun 4, 2007, at 1:37 AM, [EMAIL PROTECTED] wrote:
Revision
25876
Author
[EMAIL PROTECTED]
Date
2007-06-04 01:37:35 -0700 (Mon,
On Mon, 04 Jun 2007 17:25:13 -0700, Blair Zajac wrote:
Mark Grimes wrote:
On 6/4/2007, Blair Zajac [EMAIL PROTECTED] wrote:
I would imagine the last mile is being handled by subversion's roadmap,
but I would tend to think that in large multi-developer project's
something that coarse grain
On 2007-06-04 21:49:31 -0500, Ryan Schmidt wrote:
On Jun 4, 2007, at 21:14, Vincent Lefevre wrote:
prunille:~ port info scrollkeeper
Warning: Found 2 port scrollkeeper definitions, displaying first one.
I don't have that message when I port info scrollkeeper. Maybe you
have a local copy of a
On 5 Jun 2007, at 05:08, Vincent Lefevre wrote:
On 2007-06-04 21:49:31 -0500, Ryan Schmidt wrote:
On Jun 4, 2007, at 21:14, Vincent Lefevre wrote:
prunille:~ port info scrollkeeper
Warning: Found 2 port scrollkeeper definitions, displaying first
one.
I don't have that message when I port
On 4.6.2007, at 23.40, Ryan Schmidt wrote:
On Jun 3, 2007, at 11:09, [EMAIL PROTECTED] wrote:
Hmm. won't that cause the archive to be re-downloaded every
time you try to install, even if the archive hasn't changed? Isn't
there a syntax you can use where you tell MacPorts to store
Here's one I've never seen before... anyone else having trouble with
the MP repo? Now svk does apply props for merge tickets as mentioned
prior, and this has always worked before...
I suppose I could one-off these commits until I narrow down the
problem, but wanted to ask here at the sake of
On Jun 5, 2007, at 10:45, Mark Grimes wrote:
Here's one I've never seen before... anyone else having trouble with
the MP repo? Now svk does apply props for merge tickets as mentioned
prior, and this has always worked before...
I suppose I could one-off these commits until I narrow down the
It's not necessary to use SSL to access the repository (we use digest
authentication), and using the plain http:// URL will probably be
more robust.
- Kevin
On Jun 5, 2007, at 8:57 AM, Ryan Schmidt wrote:
Transmitting file data svn: Commit failed
(details follow):
Unfortunately, it (SSL) is actually necessary in my case (at least while
I'm at work)... Most corporate web proxies don't proxy all the HTTP
methods required to make WebDAV work. This is denoted in the form of an
Error 500.
([EMAIL PROTECTED] ~) svk sync /macports/mirror
Syncing
10 matches
Mail list logo
