All done with the erl libs thing. Upgrade to the latest version of erl On Wed, Jan 20, 2010 at 7:10 AM, Torben Hoffmann <[email protected]> wrote: > > > On Tue, Jan 19, 2010 at 22:57, Martin Logan <[email protected]> wrote: >> >> On Tue, Jan 19, 2010 at 3:36 PM, Torben Hoffmann >> <[email protected]> wrote: >> > Well, that sort of explains why my feeble attempt to locate the file >> > failed >> > so miserably! >> > >> > Maybe it is my lack of understanding of how Faxien works that throws me >> > off, >> > but if I understand you correctly the >> > >> > faxien fetch-release ... >> > >> > provides you with a "template" that should be updated to reflect the new >> > release. >> >> Faxien fetch-release really just pulls the release package and locates >> it locally. Faxien install-release goes the extra step of installing >> that package for you. Fetch release pulls the package but does not >> install it which means that the package is nicely isolated for you. >> This means you can analyse it or directly modify it and publish it >> with no distraction from other packages. > > Nice. > >> >> > >> > But what do you then do with the platform specific files in a new >> > release as >> > well as the new applications? How do you get the new versions from >> > erlang.org integrated in your system? >> >> We support mac and linux by default. If you want others you may want >> to install erlang/otp directly and leverage what is already in the lib >> dir. You can also publish those files to a local repo if you are >> working with more than one developer. > > So you actively compile Erlang for these platforms, right? (That was what I > meant by getting new versions from erlang.org). > >> >> > >> > Anyway, now that I have id'ed something I would like to change for the >> > current release how should I go about doing that? >> > The change is simple enough, though: >> > >> > ERL_LIBS=$ROOTDIR/lib:$ERL_LIBS >> > >> > A simple additing of the current ERL_LIBS variable and one is set to go. >> >> Good call - I will make the change and publish it for you. Give me a >> couple of days. > > Lovely! > > Cheers, > Torben > >> >> > >> > Cheers, >> > Torben >> > >> > >> > On Tue, Jan 19, 2010 at 19:34, Martin Logan <[email protected]> >> > wrote: >> >> >> >> the repo that contains the erlware/bin/erl file? Ahh, there is no >> >> repository that contians it actually. It is a release that lives only >> >> in the erlware repo. The process on that one is that as soon as a new >> >> version of Erlang/OTP is released we pull the erl release as such >> >> >> >> faxien fetch-release erl ./ >> >> >> >> and then modify it to reflect the latest versions of everything and >> >> publish it anew. >> >> >> >> Is that the info you are looking for? >> >> >> >> Cheers, >> >> Martin >> >> >> >> On Thu, Jan 14, 2010 at 4:22 PM, LeHoff <[email protected]> >> >> wrote: >> >> > Hi, >> >> > >> >> > I have managed to get faxien to install Erlang on my new Mac >> >> > (Snowleopard) so now I am done with other ways of installing Erlang. >> >> > >> >> > However, erlware has a fondness for overwriting the ERL_LIBS variable >> >> > which I happen to to use for an application which is not yet part of >> >> > erlware (neotoma - I will put it in when I have a setup that works >> >> > 100%). >> >> > >> >> > I would like to change erlware/bin/erl to use an existing ERL_LIBS >> >> > value instead of forcing erlware/lib on everything. >> >> > (If this is a bad thing to want please explain so I can become >> >> > wiser!) >> >> > >> >> > How do I find the repository which contains this file? >> >> > Zapping through the repos seems somewhat inefficient to me... >> >> > >> >> > Cheers, >> >> > Torben >> >> > >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups "erlware-dev" group. >> >> > To post to this group, send email to [email protected]. >> >> > To unsubscribe from this group, send email to >> >> > [email protected]. >> >> > For more options, visit this group at >> >> > http://groups.google.com/group/erlware-dev?hl=en. >> >> > >> >> > >> >> > >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "erlware-dev" group. >> >> To post to this group, send email to [email protected]. >> >> To unsubscribe from this group, send email to >> >> [email protected]. >> >> For more options, visit this group at >> >> http://groups.google.com/group/erlware-dev?hl=en. >> >> >> >> >> >> >> > >> > >> > >> > -- >> > http://www.linkedin.com/in/torbenhoffmann >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "erlware-dev" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/erlware-dev?hl=en. >> > >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "erlware-dev" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/erlware-dev?hl=en. >> >> >> > > > > -- > http://www.linkedin.com/in/torbenhoffmann > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > >
-- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
