----- Original Message -----
From: "Peter Lemenkov" <lemenkov(a)gmail.com>
To: "Sam Kottler" <skottler(a)redhat.com>
Cc: erlang-rebar-owner(a)fedoraproject.org, erlang-owner(a)fedoraproject.org
Sent: Wednesday, February 19, 2014 2:42:53 PM
Subject: Re: Bootstrapping erlang-rebar for EPEL7
Hello Sam!
2014-02-18 19:46 GMT+04:00 Sam Kottler <skottler(a)redhat.com>:
> Greetings,
>
> It's currently not possible to do a complete bootstrap of the erlang stack
> for EPEL7 because of a circular dependency in erlang-rebar. Right now
> there's a patch (rebar-0003-Remove-bundled-getopt.patch) applied to
> erlang-rebar which removes getopt from the upstream tarball.
> Unfortunately, rebar requires getopt to properly build and getopt
> subsequently requires rebar to build. Is it acceptable to remove the
> unbundling patch for the initial bootstrap (controlled via a variable I'll
> add to the spec) to get erlang-rebar built and then build erlang-getopt
> with the unbundled package?
Yes, sure! I'd start with fully bundle self-hosted rebar first and
enable all the patches next.
(sorry for the ridiculously long time since your last reply, I moved to bhutan since
then)
I just requested commit for master since I don't currently have it so I can add the
generic patch I wrote for bootstrapping there first and then just enable it for epel7.
Here's a gist of the commits in git show format (sorry about the lack of
"real" patch, but I figured the commit messages might be interesting):
https://gist.github.com/skottler/bf887642420c411ffee2. I'll push the two commits if
they look good once I get commit to master.
-s
--
With best regards, Peter Lemenkov.