Re: [sugar] [SURVEY] builders, how do you build? what do you build?
Le vendredi 27 juin 2008 à 17:23 -0400, Erik Garrison a écrit : Developers, specifically those running build systems, Many of us are confused about the software flows inherent in the daily build processes which are occuring at OLPC. I would like to conduct a simple survey of all people building software for OLPC so that all of us can better understand the sources of the software running on the XO and XS without individually hassling the responsible parties every time we have generic questions about their build processes. Builders, please describe your local build network: 0) Who are you and who do you directly work for? Guillaume Desmottes, working for Collabora Ltd. 1) What do you build? The Telepathy Stack: telepathy-gabble, telepathy-glib, telepathy-salut, telepathy-stream-engine The Farsight Stack (used for the video-chat activity): farsight, gstreamer-plugins-farsight, libjingle and sugar-presence-service. 2) Where does it come from? / Who directly provides you with source code? Most of the time I package mine own new releases (as I'm upstream of the presence-service, Gabble and Salut) or include a patch I just wrote to fix some issue. I also occasionally package latest stable releases of the rest of the stack when I need one new feature or I know it improves general stability. 3) Where does the output of your build process go? / Who handles the immediate output of your builds? Directly to Koji. 4) Where specifically is it built? (I want server names and/or descriptions, where security is a concern please share them with me privately.) My builds are submitted from teach.laptop.org to Koji. 5) What build systems do you use to build software? Please briefly describe their operation or provide a link to documentation or source code which does. No idea :) Hope that help, G. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [SURVEY] builders, how do you build? what do you build?
Erik Garrison wrote: 0) Who are you and who do you directly work for? Tomeu, contracted by OLPC. 1) What do you build? regularly: sugar, sugar-artwork, sugar-toolkit, sugar-base, sugar-datastore, journal bundle (.xo). 2) Where does it come from? / Who directly provides you with source code? Release tarballs are announced in the sugar mailing list. Snapshot tarballs are generated from git trees pulled from dev.laptop.org. 3) Where does the output of your build process go? / Who handles the immediate output of your builds? I build the rpms in fedora's koji, and from there it gets into olpc images. Not sure how it happens now though, the current process for getting the rpms into images seems to be in flux. 4) Where specifically is it built? (I want server names and/or descriptions, where security is a concern please share them with me privately.) teach.laptop.org, administered by Michael. 5) What build systems do you use to build software? Please briefly describe their operation or provide a link to documentation or source code which does. I build rpms locally (in teach) with mock (make mockbuild) and after testing I submit them to fedora's koji. See release instructions for Sugar in sugar/docs (sorry, no URL, I'm offline right now). I think it's very similar for other sugar developers. Thanks for starting this, feel free to ask any questions. Regards, Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [SURVEY] builders, how do you build? what do you build?
Am 27.06.2008 um 23:23 schrieb Erik Garrison: Developers, specifically those running build systems, Many of us are confused about the software flows inherent in the daily build processes which are occuring at OLPC. I would like to conduct a simple survey of all people building software for OLPC so that all of us can better understand the sources of the software running on the XO and XS without individually hassling the responsible parties every time we have generic questions about their build processes. Builders, please describe your local build network: 0) Who are you and who do you directly work for? Bert Freudenberg, under contract with Viewpoints Research Institute (VPRI). I usually build the rpms. Yoshiki Ohshima and Takashi Yamamiya (both employed by VPRI) do when I am unavailable. 1) What do you build? etoys rpm, squeak-vm rpm, Etoys xo bundle 2) Where does it come from? / Who directly provides you with source code? Source comes directly from VPRI. Developers there are Yoshiki Ohshima, Takashi Yamamiya, Scott Wallace, Ted Kaehler, Ian Piumarta, and y.t., directed by Alan Kay and Kim Rose. There are many more contributors from the Etoys and Squeak community, contributions are selectively pulled by the VPRI team. 3) Where does the output of your build process go? / Who handles the immediate output of your builds? rpms are pulled into the build from ~bert/public_rpms/joyride on dev.laptop.org by way of being uploaded to http://tinlizzie.org/olpc/sugar/rpm/ (a VPRI-operated server) and mirrored to http://etoys.laptop.org/rpms/ (one can also yum install from the latter) 4) Where specifically is it built? (I want server names and/or descriptions, where security is a concern please share them with me privately.) My personal machine running a virtual machine with Fedora-7. 5) What build systems do you use to build software? Please briefly describe their operation or provide a link to documentation or source code which does. http://wiki.laptop.org/go/Etoys_RPM_and_XO_bundle Note that this describes the current build process, there might be changes in the future. For example, etoys is also made available via sugar, and there was talk to get squeak and etoys into Fedora. - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [SURVEY] builders, how do you build? what do you build?
Developers, specifically those running build systems, Many of us are confused about the software flows inherent in the daily build processes which are occuring at OLPC. I would like to conduct a simple survey of all people building software for OLPC so that all of us can better understand the sources of the software running on the XO and XS without individually hassling the responsible parties every time we have generic questions about their build processes. Builders, please describe your local build network: 0) Who are you and who do you directly work for? 1) What do you build? 2) Where does it come from? / Who directly provides you with source code? 3) Where does the output of your build process go? / Who handles the immediate output of your builds? 4) Where specifically is it built? (I want server names and/or descriptions, where security is a concern please share them with me privately.) 5) What build systems do you use to build software? Please briefly describe their operation or provide a link to documentation or source code which does. In your responses please focus on the usual, simplest-case situation. The goal of this survey is to ascertain the everyday manner in which your builds progress. Feel free to include additional notes about the local network of developers you interact with--- it's fine and helpful to explain what you think happens one or two steps up or down the chain. Where possible please cc the olpc-devel list. I will take the results of this survey and produce an overview of the software flows which lead to our daily builds. As much as possible I will do this in graphical form so the results can be quickly understood by all of us. I will provide this report by email to olpc-devel as soon as possible. Thanks in advance, Erik ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [SURVEY] builders, how do you build? what do you build?
On Fri, Jun 27, 2008 at 05:23:44PM -0400, Erik Garrison wrote: 0) Who are you and who do you directly work for? Michael Stone, and Kim Quirk, respectively. 1) What do you build? Typically, rainbow, olpc-utils, puritan, and full OS builds. Occasionally, other things like sugar, X, xulrunner, initscripts, the kernel, and ejabberd. 2) Where does it come from? / Who directly provides you with source code? We can calculate commit statistics for git repositories with logic like: git log | git shortlog -s -n While there are some obvious limitations on what can be inferred from these statistics, they are perhaps helpful for pinpointing the truly guilty parties. Rather than me filling in all the details, I suggest you calculate your own results based on the public repositories on dev.laptop.org. (If you do, please remember to be careful about checking for duplicates.) As release manager, I am provided with source code from pretty much everyone. Socially, I review a lot of software for people like Martin and Scott and I review build changes for anyone who wants to make them. I think I spend most of my integration time talking with Scott, Eben, Marco, Joe, and Greg. 3) Where does the output of your build process go? / Who handles the immediate output of your builds? For packages: into a local directory, then into a webroot on dev.laptop.org, then into the OLPC package dropboxes or Fedora CVS, then into development builds, into release builds, and into manufacturing. For builds: usually into a local directory, onto a USB key, then onto an XO for personal consumption. 4) Where specifically is it built? (I want server names and/or descriptions, where security is a concern please share them with me privately.) teach, pilgrim, xs-dev, and koji.fedoraproject.org. 5) What build systems do you use to build software? Please briefly describe their operation or provide a link to documentation or source code which does. I've already written extensively about the software that I use on our wiki. Check out http://wiki.laptop.org/go/Build_system and http://wiki.laptop.org/go/Developer/Fedora Also, the Python and GNUmake manuals. Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
