byobu 5.29

Signed-off-by: Dustin Kirkland <kirkland@byobu.co>
Signed-off-by: Adam Vandenberg <flangy@gmail.com>
byobu works *much* better with tmux than screen

Closes #17221.

Signed-off-by: Dustin Kirkland <kirkland@byobu.co>
Closes #17221.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
rhash: add Lion requirement

Closes #17132.
zbar: depends on :x11
libodbc++ 0.2.5

Closes #17224.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
sbcl: add update notice for maxima

Closes #17218.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
wordplay 7.22

Closes #14295.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
wordplay: use selected compiler
qt-mobility: use upstreamed case-sensitive patch.

References #12220.
Closes #17230.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
brew upgrade: improve exit codes.

exit 1 if formulae given but none outdated

Closes #17199.

Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
bitlbee 3.2.0

Closes #17235.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
antlr 4.0

The download link to 3.5 in the old formula no longer works,
upgraded to antlr 4.0.

Closes #17238.

Signed-off-by: Adam Vandenberg <flangy@gmail.com>
tests: add mocha mocking library
build: reorganize #install for readability
ENV.with_build_environment
Allow env DSL to take a block

In addition to

  env :userpaths
  env :std

requirements can now do

  env do
    append 'PATH', '/some/path/to/bin'
    # and more
  end
Object#instance_exec for Ruby 1.8.6

Not thread safe! But I don't think we care.

We want to evaluate the env DSL block in the context of ENV for asthetic
reasons, but we also want access to methods on the requirement instance.
We can use #instance_exec to pass the requirement itself into the block:

  class Foo < Requirement
    env do |req|
      append 'PATH', req.some_path
    end

    def some_path
      which 'something'
    end
  end

Also add a simplified version of Object#instance_exec for Ruby 1.8.6.
Block-style env DSL examples
Allow satisfied? to be specified in a block

Instead of overriding #satisfied?, Requirement subclasses can specify
the condition in a block:

  satisfy do
    some_condition?
  end

The contents of the block are evaluated in the context of the instance,
and so have access to instance variables and instance methods as before.
Additionally, it is wrapped in an ENV.with_build_environment block. This
can be disabled by passing :build_env => false to satisfy:

  satisfy :build_env => false do
    some_condition?
  end
Use new requirement syntax