Skip to content
Browse files

yaws 1.94

update url/sha1

notes: yaws ships with a default configuration that expects directories to exist at:

/usr/local/Cellar/yaws/1.94/var/log/yaws
/usr/local/Cellar/yaws/1.94/lib/yaws/examples/ebin
/usr/local/Cellar/yaws/1.94/lib/yaws/examples/include

and attempts to host a server on port 80/443

the practical upshot of this is that out of the box yaws will load, throw a warning about the directories above, and die.  supplying them will fail at the ports step because yaws expects to have root level permissions.

tl;dr- should we add a message warning about the above to the caveats part of the script?
  • Loading branch information...
1 parent f84d9a4 commit a99281d8ae8ab5be4adc0161c6c6138003c081f6 @asparagui committed Jul 13, 2012
Showing with 20 additions and 2 deletions.
  1. +20 −2 Library/Formula/yaws.rb
View
22 Library/Formula/yaws.rb
@@ -2,8 +2,8 @@
class Yaws < Formula
homepage 'http://yaws.hyber.org'
- url 'http://yaws.hyber.org/download/yaws-1.92.tar.gz'
- md5 'd0c05d2041df79089f7de5d8437ee34b'
+ url 'http://yaws.hyber.org/download/yaws-1.94.tar.gz'
+ sha1 '36295e40bb4db1812901c31d41152f942a63b5cc'
depends_on 'erlang'
@@ -39,6 +39,24 @@ def caveats; <<-EOS.undent
Usually you want to build yapp (yaws applications) as well.
To do so, use:
brew install yaws --with-yapp
+
+ NOTES
+ A) yaws ships with a default configuration that
+ expects the following directories to exist:
+
+ #{prefix}/var/log/yaws
+ #{lib}/yaws/examples/ebin
+ #{lib}/yaws/examples/include
+
+ and will halt if it does not find them. Either reconfigure
+
+ #{etc}/yaws/yaws.conf
+
+ or create these directories to proceed.
+
+ B) The default configuration will also attempt to host a server
+ on ports 80 and 443 and will fail unless you run yaws
+ interactively as root (sudo yaws -i) or modify yaws.conf.
EOS
end
end

0 comments on commit a99281d

Please sign in to comment.
Something went wrong with that request. Please try again.