<feed xmlns='http://www.w3.org/2005/Atom'>
<title>puppet.git/ext/envpuppet, branch master</title>
<subtitle>Puppet repo</subtitle>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/ricky/public_git/puppet.git/'/>
<entry>
<title>(#6395) Add extpuppet help, eval, and interfaces</title>
<updated>2011-05-19T23:49:49+00:00</updated>
<author>
<name>Jeff McCune</name>
<email>jeff@puppetlabs.com</email>
</author>
<published>2011-02-21T20:34:31+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/ricky/public_git/puppet.git/commit/?id=f037662edfd35a9b0f17cab45ba30753c3959a0c'/>
<id>f037662edfd35a9b0f17cab45ba30753c3959a0c</id>
<content type='text'>
This patch add three features to the envpuppet helper script.

First, if --help is passed as the first argument, a helpful message is
printed.

Second, if ENVPUPPET_BLEEDING=true when envpuppet is executed,
additional repositories are enabled.  The only addition at this time is
puppet-interfaces, which heavily modifies the behavior of Puppet itself
and may or may not be desired.

Third, if no arguments are passed to the script, bourne compatible shell
statements are printed to STDOUT which may be directly evaluated in the
current shell.  This is to help people who prefer to directly set
RUBYLIB and PATH in their development workflows, which I've noticed to
be the case for many people.

For example:

    eval $(envpuppet)

Signed-off-by: Jeff McCune &lt;jeff@puppetlabs.com&gt;
Reviewed-by: Jacob Helwig &lt;jacob@puppetlabs.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch add three features to the envpuppet helper script.

First, if --help is passed as the first argument, a helpful message is
printed.

Second, if ENVPUPPET_BLEEDING=true when envpuppet is executed,
additional repositories are enabled.  The only addition at this time is
puppet-interfaces, which heavily modifies the behavior of Puppet itself
and may or may not be desired.

Third, if no arguments are passed to the script, bourne compatible shell
statements are printed to STDOUT which may be directly evaluated in the
current shell.  This is to help people who prefer to directly set
RUBYLIB and PATH in their development workflows, which I've noticed to
be the case for many people.

For example:

    eval $(envpuppet)

Signed-off-by: Jeff McCune &lt;jeff@puppetlabs.com&gt;
Reviewed-by: Jacob Helwig &lt;jacob@puppetlabs.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>(#5062) Add envpuppet helper script to ext/</title>
<updated>2010-10-25T23:37:59+00:00</updated>
<author>
<name>Jeff McCune</name>
<email>jeff@puppetlabs.com</email>
</author>
<published>2010-10-20T22:22:06+00:00</published>
<link rel='alternate' type='text/html' href='https://fedorapeople.org/cgit/ricky/public_git/puppet.git/commit/?id=4d1681e05a187e55422bf00de5c932736548be15'/>
<id>4d1681e05a187e55422bf00de5c932736548be15</id>
<content type='text'>
This script helps people quickly test different branches of various
puppet related projects like facter, puppet-scaffold, puppet-dashboard,
etc...  It allows the user to simply clone puppet and start running
different puppet version without installing puppet or any other setup
costs.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This script helps people quickly test different branches of various
puppet related projects like facter, puppet-scaffold, puppet-dashboard,
etc...  It allows the user to simply clone puppet and start running
different puppet version without installing puppet or any other setup
costs.
</pre>
</div>
</content>
</entry>
</feed>
