On Apr 27, 2009, at 18:45, Rainer Müller wrote:
nox wrote:
I haven't looked at the source but I think it just searches $
{version}
in the Portfile after having read it, and triggers the warning if
it's
not the version command. So if I'm right, the answer is yes.
The regex currently being
On Apr 27, 2009, at 18:27, dwe...@macports.org wrote:
Revision: 50222
http://trac.macports.org/changeset/50222
Author: dwe...@macports.org
Date: 2009-04-27 16:27:01 -0700 (Mon, 27 Apr 2009)
Log Message:
---
The default installation with shared libraries appears to work no
On Apr 27, 2009, at 4:43 PM, Darren Weber wrote:
Seems that the svn lint checker is different from the port lint
checker, ie:
The server uses a recent trunk build, so it could be different than
your local version.
-Bill
___
macports-dev m
nox wrote:
> I haven't looked at the source but I think it just searches ${version}
> in the Portfile after having read it, and triggers the warning if it's
> not the version command. So if I'm right, the answer is yes.
The regex currently being used for exclusion is
{^PortSystem|^PortGroup|^v
Seems that the svn lint checker is different from the port lint checker, ie:
[ m...@xxx ~/ports ]$ port lint vtk-devel
---> Verifying Portfile for vtk-devel
---> 0 errors and 0 warnings found.
On Mon, Apr 27, 2009 at 4:40 PM, Perry Lee wrote:
> On Apr 27, 2009, at 4:32 PM, Darren Weber wr
On Apr 27, 2009, at 4:32 PM, Darren Weber wrote:
How do we specify that a variant conflicts with several other
variants. Lint indicates a problem with this syntax:
variant carbon conflicts {cocoa x11} description {Build with Carbon} {
...
}
variant carbon conflicts cocoa x11 description {B
How do we specify that a variant conflicts with several other variants.
Lint indicates a problem with this syntax:
variant carbon conflicts {cocoa x11} description {Build with Carbon} {
...
}
Should it be:
variant carbon conflicts cocoa x11 ...
or maybe:
variant carbon conflicts cocoa conflict
Le 27 avr. 09 à 20:30, Ryan Schmidt a écrit :
On Apr 27, 2009, at 08:56, nox wrote:
Using php5*extension also makes this lint test reports false
positive as
php5extension.setup sets ${version} itself.
I haven't run trunk in awhile so I haven't seen this problem yet.
php5extension.setup wa
On Apr 27, 2009, at 08:56, nox wrote:
Using php5*extension also makes this lint test reports false
positive as
php5extension.setup sets ${version} itself.
I haven't run trunk in awhile so I haven't seen this problem yet.
php5extension.setup was modeled on other portgroups -- the ruby,
has
For development of ports, we can use a local repository as a sandbox to test
port changes before adding back to the trunk. Would it be possible to set
some general configuration options that apply to any ports from this local
repository?
For example, the local repo is at ~/ports and it contains a
Le 27 avr. 09 à 01:28, Rainer Müller a écrit :
Ryan Schmidt wrote:
On Apr 25, 2009, at 19:36, Jeremy Huddleston wrote:
Portfile: firefox-x11-devel Warning: Line 163 seems to hardcode
the version number, consider using ${version} instead
Can this check please be updated to not report false-po
11 matches
Mail list logo
