watson.timothy at gmail.com
Thu Aug 2 19:06:46 EDT 2012
On 28 July 2012 19:17, Tuncer Ayaz <tuncer.ayaz at gmail.com> wrote:
> On Fri, Jul 27, 2012 at 3:05 PM, Eric Merritt wrote:
>> that makes sense, but you should have deprecation window (maybe the
>> R16 release). Supporting ancient versions takes time, adds
>> complexity and failure modes that would not otherwise be there. So
>> set an explicit 'no longer officially supported' date. There will
>> probably be some back and forth with users that care but at least
>> they will know when things are no longer going to be supported and
>> can plan and you know when you can remove dead code and work arounds
>> for ancient brokenness.
> Makes sense, but the most important reason for keeping compatible
> with 13B03 is that it has been chosen by a few long term linux distro
> We already have one TODO item about erlang:halt stdout flushing being
> fixed in 15B01 and therefore removing the need for the workarounds.
> Another one is that reltool.app was not installed before a certain
> release and we therefore have to rely on code:lib_dir/1 instead of
> application:get_key for checking the reltool version.
> Still, I agree that we should lay out a plan for how long certain OTP
> versions are still supported.
Sadly for me, my day job requires supporting Erlang versions as old as
R12B, so I can't use rebar for our build system there, which is a real
shame. Maybe if I write some bonkers external_compile_plugin that
breaks out to the shell, but by the time I've done all that malarkey
we might as well just stick with the make based build system we've got
More information about the rebar