Re: Whitespaces in Portfile
On Jul 16, 2008, at 16:08, Uwe Schwartz wrote: > Rainer Müller schrieb: > >> Uwe Schwartz wrote: >> >>> are there any conventions about tabs and whitespaces in Portfile? >>> I couldn't find any hints in the wiki or in the guide. >> >> http://guide.macports.org/#development.practices.portstyle >> >> Additionally, watch out for trailing whitespace - especially when the >> line should end with a backslash. Use 'port lint', it prints a >> warning >> for this. > > 'port lint' is much more convenient than 'portindex' Some whitespace warnings that port lint currently prints will be removed or will only appear when using a switch: http://trac.macports.org/ticket/14799 port lint does not currently warn if you use tabs in your portfile, though spaces are preferred instead of tabs. ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Whitespaces in Portfile
'port lint' is much more convenient than 'portindex' Thanks. Uwe Rainer Müller schrieb: > Uwe Schwartz wrote: >> are there any conventions about tabs and whitespaces in Portfile? >> I couldn't find any hints in the wiki or in the guide. > > http://guide.macports.org/#development.practices.portstyle > > Additionally, watch out for trailing whitespace - especially when the > line should end with a backslash. Use 'port lint', it prints a warning > for this. > > Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Whitespaces in Portfile
Uwe Schwartz wrote: > are there any conventions about tabs and whitespaces in Portfile? > I couldn't find any hints in the wiki or in the guide. http://guide.macports.org/#development.practices.portstyle Additionally, watch out for trailing whitespace - especially when the line should end with a backslash. Use 'port lint', it prints a warning for this. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Whitespaces in Portfile
Hi, are there any conventions about tabs and whitespaces in Portfile? I couldn't find any hints in the wiki or in the guide. Regards, Uwe ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: To whom should error messages be written?
On Jul 15, 2008, at 11:43 PM, Ryan Schmidt wrote:
> I think we should write error messages to the end user, not the
> portfile developer. I think we should also have a new page in the
> wiki called ErrorMessages, where we can list the error messages that
> MacPorts might print along with explanations of what the portfile
> author should do about them. We would describe mtree violations and
> ineffectual reinplaces and checksum failures (the checksum failure
> discussion would move to this new page from the FAQ).
I think you've highlighted an important point ("what audience are
these messages for?") but I don't necessarily see this as an either/or
scenario. Both types of messages are important, depending on the
context, we've just done a poor job of segregating them and allowing
the user or developer to select which types they want. I think
there's enough goop being generated at this point that it would be a
fine (and comparatively easy) project to add some classification
attributes to each messages and then enhance the port command to allow
messages to be emitted by classification (with, of course, some good
defaults for naive users). This is the ASL approach, and while it's
taken awhile for ASL to gain traction in MacOSX, people are already
using it to do some rather sophisticated log generation and
scraping. I understand that these are not log messages, but they're
close enough in spirit and form that we should take a page from ASL's
book when it comes to attributes and uniform structure of each
message. This would be particularly helpful for debugging messages,
where we've currently dumped so much stuff into one big "debug bucket"
that it becomes increasingly more difficult to read the output of port
-d.
- Jordan
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Meaning of "Not a directory"
On Mon, Jul 14, 2008 at 4:35 PM, Rainer Müller <[EMAIL PROTECTED]> wrote:
> Rainer Müller wrote:
>> I think there is some problem with the python25 framework port. I can
>> reproduce the message here and will see if I can find a solution.
>
> I am still trying to figure out where graphviz or swig pick up the path
> to the framework directory, but I can't find it. It needs to be changed
> to point to ${prefix}/lib/python25 instead there. Any help appreciated.
Does anyone know how to fix this or where ./configure or the linker
picks up the path to Leopard's built-in Python?
I can not find where the wrong path comes from either. The path
returned by the Python snippet in the ./configure points to the
correct Python location (/opt/local/...) and yet the library gets
linked against the system Python. Here is the path returned by Python:
>>> print sys.prefix
/opt/local/Library/Frameworks/Python.framework/Versions/2.5
Perhaps we should file a ticket for this bug (especially if we do not
solve it right away), but what port should it be filed against?
Python, SWIG or every individual port which has problems with
SWIG-generated Python bindings?
Uldis
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: base from trunk fails to install with "install: /opt/local/share/macports/: No such file or directory"
Adam Mercer wrote: > Just tried to install base from the trunk and install fails with the > following error: > > /usr/bin/install -c -o root -g admin -m 444 setupenv.bash > /opt/local/share/macports/ > install: /opt/local/share/macports/: No such file or directory > > manually creating this directory and the installation proceeds without error. Thanks for the report. I just never tested this addition with a fresh install. Fixed in r38344. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Re: Chunked guide
On Jul 16, 2008, at 6:13 AM, Simon Ruderich wrote: PS: Looks like the guide doesn't get updated anymore. I made some changes yesterday and they are still not available at guide.macports.org. Fixed. -Bill smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Chunked guide
Hi, I just committed a new target "guide-chunked" to the doc-new Makefile which generates a chunked version of the guide [1]. I used a Tcl script to add the table of contents to each page. Please have a look at [2] and tell me what you think. If you like it we can activate the guide-chunked target on the documentation server and make it available to everybody. Thanks, Simon PS: Looks like the guide doesn't get updated anymore. I made some changes yesterday and they are still not available at guide.macports.org. [1]: http://trac.macports.org/changeset/38342 [2]: http://ruderich.com/macports/chunked/ -- + privacy is necessary + using http://gnupg.org + public key id: 0x6115F804EFB33229 pgpDld28w3pBz.pgp Description: PGP signature ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
