Skip to content
This repository has been archived by the owner on May 12, 2018. It is now read-only.

simplenode.reltool.config: use default sys-level mod_cond setting #43

Merged
merged 1 commit into from Apr 10, 2013
Merged

simplenode.reltool.config: use default sys-level mod_cond setting #43

merged 1 commit into from Apr 10, 2013

Conversation

ghost
Copy link

@ghost ghost commented Dec 13, 2012

As discussed here change the reltool spec to use the default sys-level mod_cond setting.

@essen
Copy link

essen commented Dec 13, 2012

+1

2 similar comments
@naiquevin
Copy link

+1

@jimymodi
Copy link

+1

@essen
Copy link

essen commented Dec 16, 2012

Less happy about the current patch. People will uncomment it thinking it's safe and then find out their release won't work and unless they really know reltool they won't know how to make it work. It's not a magical option you can change to make the release smaller, there's a lot more to it than that.

Either remove entirely or just leave {mod_cond, all} like we had before IMO.

@joewilliams
Copy link
Contributor

+1

@ghost
Copy link
Author

ghost commented Apr 6, 2013

@essen amended the commit to completely remove the non-default sys-level mod_cond and did the same in https://github.com/rebar/rebar/wiki/Release-handling. Also see http://erlang.org/pipermail/erlang-questions/2013-April/073185.html

As discussed here
http://erlang.org/pipermail/erlang-questions/2012-December/071135.html
change the reltool spec to use the default sys-level mod_cond setting.
dizzyd added a commit that referenced this pull request Apr 10, 2013
simplenode.reltool.config: use default sys-level mod_cond setting
@dizzyd dizzyd merged commit 98d7ec9 into rebar:master Apr 10, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
5 participants