software based on it. Though about yaws:
$ port search yaws
yaws @1.76 (www)
Webserver for dynamic content written in Erlang
Hm. I don't know what i have been looking at yesterday.
Thanks for catching that.
--
Florian Ebeling
[EMAIL PROTECTED]
There are a number of error messages that MacPorts might print during
the normal course of events. Checksum errors, fetch failures, port
misbehaviors. Who should be the audience for these error messages --
the end user or the portfile developer? I would argue the former but
we currently
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
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
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
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
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
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
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
'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
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,
11 matches
Mail list logo