On Sep 7, 2007, at 5:34 AM, N_Ox wrote:
Shouldn't these paths be absolute paths? I didn't think the cwd
was guaranteed to be anything in particular. I'm surprised that
the cd command above works.
I've always used cd and it has always worked.
It works right now, but there have been some
Le 7 sept. 07 à 01:10, Ryan Schmidt a écrit :
On Sep 6, 2007, at 07:27, [EMAIL PROTECTED] wrote:
Revision: 28665
http://trac.macosforge.org/projects/macports/changeset/
28665
Author: [EMAIL PROTECTED]
Date: 2007-09-06 05:27:36 -0700 (Thu, 06 Sep 2007)
Log Message:
On Sep 4, 2007, at 12:03 PM, Ryan Schmidt wrote:
Very sorry! That was my fault. I've now fixed the svn:date
property of revision 2 so the log should work again. The timestamp
of revision 1 and revision 3 are identical, so I set revision 2 to
that same timestamp.
(I issued a bad svn
Last time this was brought up only one person complained, but it
really is a serious problem and we need standards. Therefore I
propose the following:
* All source code files MUST use soft tabs at a tabstop of 4. No
hard tabs are allowed.
* All source code files SHOULD have the following
On Sep 7, 2007, at 1:44 PM, Blair Zajac wrote:
Kevin Ballard wrote:
* Makefiles MUST use tabs as it is required by the syntax.
Makefiles SHOULD use a tab stop of 4.
I suggest using a tab stop of 8. I never have modelines in my
Makefile's so seeing a tab stop of 4 would look odd.
Fair
On Sep 7, 2007, at 1:31 PM, Kevin Ballard wrote:
Last time this was brought up only one person complained,
?? Every few months this comes up. There are a few people vocally in
favor of one way or another to do things. I think most people don't
care too much.
but it really is a serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Kevin Ballard wrote:
Last time this was brought up only one person complained, but it really
is a serious problem and we need standards. Therefore I propose the
following:
If I remember correctly, last time was decided every port maintainer can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Blair Zajac wrote:
Why is it that most well known open-source projects have formatting
rules that they abide to, even if some people personally don't like
them. For example, the Subversion project uses the GNU C coding style,
which I don't use
* Why have rules for Portfiles? Isn't that the maintainer's prerogative?
Yes it is, which is why I marked those rules as SHOULD rather than
MUST. Having consistent rules for Portfiles aids reading of
Portfiles, especially if the Portfile is marked openmaintainer@ as
those are edited by
macports-dev@lists.macosforge.org writes:
Added: trunk/base/HACKING (0 = 28702)
--- trunk/base/HACKING (rev 0)
+++ trunk/base/HACKING 2007-09-07 18:34:33 UTC (rev 28702)
@@ -0,0 +1,13 @@
+Whitespace rules as discussed on the list:
+
+* All source code files MUST use soft
The work on the new guide is progressing steadily, but one thing has
become apparent. We need to unify our documentation efforts. The
manpages proceed on a separate path from the guide docs, and we on the doc
team (Maun Suang , Simon Ruderich, and I) think that the man pages should
be rewriten
I am unfortunately late to reply to this thread, even though it was
me who encouraged Kevin to start it.
Top posting to make a couple of general comments, I just wanted to
state, officially and for the record (and yes, with my project
manager hat on), that I am strongly supporting
On Sep 7, 2007, at 09:43, Rainer Müller wrote:
Landon Fuller wrote:
On Sep 4, 2007, at 12:03 PM, Ryan Schmidt wrote:
Very sorry! That was my fault. I've now fixed the svn:date property
of revision 2 so the log should work again. The timestamp of
revision
1 and revision 3 are identical,
On Sep 7, 2007, at 14:29, Blair Zajac wrote:
Landon Fuller wrote:
On Sep 7, 2007, at 09:43, Rainer Müller wrote:
It's nice to fix typos in log messages. But it could be limited to
svn:log for that purpose with a pre-revprop-change like this:
The log being unversioned, that still seems a
Landon Fuller wrote:
On Sep 7, 2007, at 14:29, Blair Zajac wrote:
Landon Fuller wrote:
On Sep 7, 2007, at 09:43, Rainer Müller wrote:
It's nice to fix typos in log messages. But it could be limited to
svn:log for that purpose with a pre-revprop-change like this:
The log being unversioned,
On Sep 7, 2007, at 16:19 , Kevin Ballard wrote:
vim:
sts=4
soft tab stop is 4
FWIW, I'm partial to :smarttab (:sta), but I haven't compared it
to :sts in a while so I can't really comment on the mertis of one
over the other. Maybe they aren't mutually exclusive?
Dave
Hello,
I submitted a ticket for nco-3.9.2 (belongs to science).
Thanks.
Takeshi
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev
17 matches
Mail list logo
