On Feb 24, 3:55 pm, Dave Smith <[email protected]> wrote:
> Before I continue, please note that the following instructions are for
> bootstrapping a COMPLETE repo. The intent is not to use the public
> repo at all and the intent is to build a copy of faxien that uses the
> erts version you desire. These instructions may need some tweaking --
> please read through the scripts referenced below before deluging us
> with questions. :)
>
> It's non-trivial to bootstrap an entire repo -- but here are the rough
> instructions, using my faxien repo athttp://github.com/dizzyd.
>
> 0. Make sure you have neither faxien or erlang on your current path.
> 1. Build vanilla erlang of the target version
>
> ./configure --prefix=/Some/Temp/Directory && make && make install
> export PATH=/Some/Temp/Directory/bin:$PATH
>
> We need this vanilla erlang to build faxien -- but we won't be
> using it for our actual deployment.
>
> 2. Grab faxien from my github repo.
>
> cd faxien/scripts/bootstrap && ./bootstrap
I got this:
cd faxien/scripts/bootstrap && ./bootstrap
Downloading eunit...done.
Downloading cryptographic, ewlib, ewrepo and gas...done.
Downloading epkg and faxien...sed: can't read s/ERTS_VSN=.*/
ERTS_VSN=5.6.5/g: No such file or directory
Ok, I'm using our own R12B-5 copy, but it is built and installed
exactly as the vanilla one from erlang.org
--Tobbe
>
> This will leave you with a "faxien-installer-i386-darwin-9.sh"
> script. This is a fresh build of the latest faxien (well latest in my
> repo, anyways).
>
> 3. Install the new faxien build
>
> sh faxien/scripts/bootstrap/faxien-installer-i386-darwin-9.sh `pwd`
>
> You should now have a erlware directory in `pwd`. Add erlware/bin
> to your path and adjust faxien to point to your own internal webdav
> server; remember the assumption here is that you are boostrapping
> EVERYTHING, so you really don't want to use the public repo.
>
> 4. Build/publish erlang using new faxien.
>
> Now we want to remove the erlang path we added in step 1; all we
> want on our path is faxien. Once this is done:
>
> cd faxien/scripts && python faxien-auto-publish.py
>
> 5. Publish erl package.
>
> We want the runtime and compiler to be available in our new repo.
>
> cd faxien/scripts && ./make-erl.sh 0
>
> You should now have a nice erl release in release directory -- publish it.
>
> cd release && faxien publish erl-*
>
> That's the gist of it.
>
> D.
>
> On Tue, Feb 24, 2009 at 2:06 AM, dysinger <[email protected]> wrote:
>
> > I have been using 12B-5 for months and would like to use sinan with
> > it. 13A-0 is being previewed right now too.
>
> > How would I package and release all the core apps from OTP for my
> > version of erlang? Is that possible? What are the steps ? I have
> > sinan.git and faxien.git locally.
>
> > -Tim
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
