Welcome to the Jungerl!

[Sean Hinde]

Hi,

Great stuff..

> 1. The build scripts assume "include" directories, but some 
> are just named 
>      "inc". Which is the preferred way for Erlang?

Well I'd vote for include - like all the OTP libs.

> 2. Some libs, like xmerl,  has a later version in another cvs 
> repository 
>     under sourceforge. How will they be kept in sync? What happens
>     if anyone updates the one under jungerl. Will the admin 
> of the other
>     one see to it that they are in sync, or shall we expect 
> them to diverge,
>     or shall they all go under the jungerl tree?

I'd say something like xmerl really warrants its own project. Perhaps when
things get big enough or well established enough they should be bumped up a
level.

I'll also contribute a bunch of stuff from our cvs repository. I've had a
few things in mind to release for ages but never quite polished them up to
contrib standard (I'm thinking erlang cvs driver and repository consistency
checker, and a .rel, .app.src to finished build tool, as well as a bunch of
other random stuff).

I do think this will need some active management from someone who gets a
kick out of organising things (i.e. defintely not me!) To be useful for the
widest audience we really need to avoid it becoming Junkerl.. Like should we
have a new project called
random_build_tools_which_are_all_useful_but_dont_work_together?! I guess the
project mailing list is the place to sort these issues out.

Sean



 NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.