[erlang-questions] Building, Packaging and Installing

[Bob Ippolito]

That's a nice idea, but it's not very practical to add a dependency on GHC
to Erlang users, although if we're just talking server-side then that might
be an ok solution.

I think we just need to clearly identify what needs to be improved and just
fix rebar, anger or sinan to do that. I don't care which one it is, as long
as there's a de facto standard. Rebar feels pretty close to standard at
this point, so if we can fix it then we'll get the most bang for our buck.

On Saturday, May 5, 2012, Tristan Sloughter wrote:

> Tuncer's idea of Hackage for Erlang is interesting. And if it were
> possible to move something like Hackage to do for Erlang what it does for
> Haskell, instead of writing from scratch, that could be even better.
>
> Tristan
>
> On Fri, May 4, 2012 at 2:32 AM, Tim Watson <watson.timothy@REDACTED>wrote:
>
> Is Columbo somehow different from what rebar already does in this space?
>
>
>
> On 4 May 2012, at 03:06, Tristan Sloughter <tristan.sloughter@REDACTED>
> wrote:
>
> Ah yes, I briefly looked at colombo when you mentioned it on the erlware
> list. I'll give that a deeper look to see how much of what I need is
> covered by it and possibly simply start extending it.
>
> Tristan
>
> On Thu, May 3, 2012 at 4:52 PM, Torben Hoffmann <torben.lehoff@REDACTED>wrote:
>
> That actually sounds like a good step forward - it almost, but only almost
> makes me sad that I have created my own dependency management tool called
> colombo (alpha vers. is on github/lehoff).
>
> I haven't spent much time on it, but it can fetch apps from git repos as
> well as their dependencies,  one can specify a tag or a branch to check
> out, a simple build can be done and you can get a version tagged version
> installed in the subdir lib of the dir where you you colombo (vers is taken
> from the app file or a default is choosen).
>
> very much alpha quality, but it shows that small dedicated tools aren't
> that hard to create for the Erlang eco system.
>
> I will continue improving colombo since it helps me solve my own problem,
> but it would be nice to have "real" users as well that could help form the
> functionality of the tool. Or tools since I might already have added too
> much functionality to colombo.
>
> Cheers,
> Torben
>
> Sent from my iPad
>
> On 03/05/2012, at 15.30, Tristan Sloughter <tristan.sloughter@REDACTED>
> wrote:
>
> I feel like someone said Travis-CI wasn't the answer... But I am now
> having the thought it is, at least to make something I'd like to see
> without me having to do it.
>
> The question is would the community be interested in this if
> I implement it. Here is what I'm talking about:
>
> 1) A github hook that informs X that an update to a branch or tag is
> pushed.
> 2) This hook does not only ensure tests pass but also that the version
> numbers are correct. If you tag a project as 0.1.0 and the .app file has
> {vsn, 0.1.0} it fails
> 3) Assuming these criteria are met the agner repo for the project is
> either updated or created. Instead of @master it would use a piece of the
> git hash for the branch pointer (using a moving target -- a branch name --
> as the version of an app doesn't make sense), for a tag it would use the
> tag name.
>
> Now, this is only part of the large solution people want, and I agree with
> them we should do.
>
> But, I think it is a start and something that can be done in small enough
> amount of effort to be done soon.
>
> Tristan
>
> On Wed, May 2, 2012 at 7:18 PM, Tim Watson <watson.timothy@REDACTED>wrote:
>
> On 02/05/2012 21:13, Ciprian Dorin Craciun wrote:
>
> On Wed, May 2, 2012 at 11:03 PMv, Tim Watson<watson.timothy@REDACTED**com>
>  wrote:
>
>  Eric Merit and I have had some lengthy discussions about this on the
> Erlware mailing list and have some ideas that I think are pretty solid.
>
>     I'm glad to hear this. (I'll give it a look.)
>
> Cool than
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120505/efb6ac0e/attachment.htm>