rebar3.git - Clone of https://github.com/erlang/rebar3

	Commit message (Collapse)	Author	Age	Files	Lines
*	remove more code that can be brought back later if needed	Tristan Sloughter	2014-08-30	1	-44/+0
\|
*	Sync test/upgrade_project/rel/files with priv/templates	Tuncer Ayaz	2013-06-12	1	-7/+17
\|
*	Use "pwd -P" to get the current physical path.	olgeni	2013-06-10	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	It is a portable version of the realpath(1) utility that you can find on Mac OS X and FreeBSD (see also The Open Group Base Specifications Issue 6, IEEE Std 1003.1). Without the -P flag, pwd(1) might return different values when the current path contains one or more symlinks, depending on how you got into the current directory. In simplenode.runner, this may cause PIPE_DIR to have different values on each use, which will make it impossible to connect to the running node unless you guess the correct path yourself.
*	Sync rel/files in dummy project with templates	Tuncer Ayaz	2011-07-18	1	-1/+1
\|
*	Add 'generate-upgrade' command	joewilliams	2011-01-27	1	-0/+34
	To support OTP release upgrades I have added support for building upgrade packages. Support for this is included in the rebar_upgrade module, specifically generate_upgrade/2. It requires one variable to be set on the command line 'previous_release' which is the absolute path or relative path from 'rel/' to the previous release one is upgrading from. Running an upgrade will create the needed files, including a relup and result in a tarball containing the upgrade being written to 'rel/'. When done it cleans up the temporary files systools created. Usage: $ rebar generate-upgrade previous_release=/path/to/old/version This also includes a dummy application that can be used to test upgrades as well as an example. Special thanks to Daniel Reverri, Jesper Louis Andersen and Richard Jones for comments and patches.