Le 13 juil. 2012 02:49, "Gerd Stolpmann" <i...@gerd-stolpmann.de> a écrit : > > Am 13.07.2012 02:06:23 schrieb(en) Sylvain Le Gall: > >> ... >> ===> Bootstrap successful >> >> Great ! > > > Hey, excellent! > > [...] >> Command returned with non-zero exit code >> Error: Command fails with code 1: godi_console >> >> But that is expected and is due to the "@". Maybe we should patch it >> as D. Doligez describe it (i.e replace it by "A@A"). > > > Choosing the @ char was a bit unfortunate. It always conflicts with the > responsefile feature, even if this feature should be disabled in OCaml one > day, as there can be wrappers around it. I guess we have no other alternative > than the A@A trick. > > >> So here are the issues, I encounter: >> - needs to install gcc-core and binutils >> - problem with janestreet-core unzipping >> - missing GODI_USER in godi.conf > > > Only the unzip problem is a hard one. > > >> I use a Win7/VM. I made a snapshot before beginning to build GODI. >> When you have a new godi-skylift version, I can go back to the >> snapshot and test again (until it works). > > > Ok, I've just changed the bootstrap so a better exception is printed for > unzip, including the full command. >
OK, tell me when a new skylift tarball is ready. I can test it on sunday or monday evening. > >> Concerning the "future" of all this -- because I want GODI to work on >> Windows on the long term, not just as single shot -- I can propose you >> to run a @weekly or @daily job that will build GODI skylift for you on >> Windows/Mac OS X/Linux. All I need is an access to a VCS that gives me >> the state of GODI (i.e. a commit in this VCS will trigger a build). >> >> Are you interested ? > > > Yes, I am. Finally the GODI-on-Windows journey makes sense. > > Concerning the trigger for packages, this is easy: just check whether > "godi_console update" finds updates. (I've a script for this.) For the whole > bootstrap: There is no automatic definition when a new testable bootstrap is > ready. Sometimes the bootstrap is ready, but it needs a package update before > it can work. I'd go here for a manual trigger. > Manual triggering works as well, also we will need a VCS anyway to store the continuous integration script. Can you tell how you build the skylift tarball itself. > Regarding the Windows port, how far would you go? I always found it > reasonable to provide a binary release, as many Windows users get scary when > it comes to software builds. But I never found the time to do this, and hoped > a group of interested people could maintain such a release. Skylift has now > the required features: Users can download binary packages from remote > repositories as if they were local. The format of the binary packages was > extended for ensuring binary compatibility (the checksum thing). For > publishers, there is scripting support for copying the packages to a public > directory. I could imagine we could attract a lot more beginners and serious > users with such a release. > Lets start small. Make the GODI build process (and a few selected packages) works as reliably as possible. Once we will have time and be confident in process, we can use the builder to publish binary packages required to do the bootstrap. If we can get to the point that we can create a binary installer that will help to skip all the initial bootstrap process, it will be a big Win and a very argument for beginner. I see some problems however, to reach this state: - GODI binary packages need to be relocatable, i.e. forcing the standard directory to be c:\cygwin\opt\godi would feel strange for a Windows guy - some packages are definitively not relocateable (camomile e.g.), we will need to skip them - once relocated we should be able to continue using GODI FYI, if we are able to do it for Windows, we can also create such installer for Mac and Linux with little additional effort. Does skylift bootstrap process produces the binary packages ? If this is the case, where are they located ? If the binary packages are there, providing them is a matter of second. Cheers Sylvain _______________________________________________ Godi-list mailing list Godi-list@ocaml-programming.de https://godirepo.camlcity.org/mailman/listinfo/godi-list
