[ANNOUNCE] first release of Inferno bundles for OLPC.
I've posted the first release of my Inferno bundles for the OLPC. They can be grabbed from Google Code (http://code.google.com/inferno-olpc), but it doesn't look like Google has the xo or xol mime-types installed, so if you are downloading directly onto an OLPC its probably best to download them from the OLPC Wiki (http://wiki.laptop.org/go/Inferno). These packages work on my stock G1G1 laptop, I haven't tried with any of the newer development builds. Please submit bug reports through the Google Code interface. This is only the initial release, meant primarily to test packaging. Further releases will deal with integrating Inferno more closely with the OLPC environment and customizing fonts and color schemes as well as application interfaces to the smaller form factor. -eric ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Adding content to the XO
On Jan 2, 2008 11:10 PM, Benj. Mako Hill <[EMAIL PROTECTED]> wrote: > > > I'm running with a stock laptop from the G1G1 program, the > > instructions on the library grid (in the wiki) don't seem to match > > what I see on my XO -- there is no /home/olpc/Library > > Strange. It should exist or should be created when you try to install an XOL. > The fact that the auto-install wasn't working was due to me not having the right mime types configured on my web server. Things seem to be okay now, I've written up my experiences and added them to the wiki: http://wiki.laptop.org/go/Experiences_with_adding_content -eric ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Adding content to the XO
On Jan 2, 2008 11:10 PM, Benj. Mako Hill <[EMAIL PROTECTED]> wrote: > > > I'm running with a stock laptop from the G1G1 program, the > > instructions on the library grid (in the wiki) don't seem to match > > what I see on my XO -- there is no /home/olpc/Library > > Strange. It should exist or should be created when you try to install an XOL. > Yes - the download seemed to succeed, but the content never showed up, so I was trying to fault isolate. It'd be really nice for someone to build a "bundle verification" suite for content as well as activities that is a bit more verbose on errors. > > - let alone a /home/olpc/Library/makeindex.py > > This is incorrect. The file is /usr/share/library-common/make_index.py > and it's been there since Ship.2 > > Where did you find this documentation? It seems either very out of date > or simply incorrect. > It was in the Library Grid wiki page, I can update it once I validate the process. -eric ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Adding content to the XO
I'm running with a stock laptop from the G1G1 program, the instructions on the library grid (in the wiki) don't seem to match what I see on my XO -- there is no /home/olpc/Library - let alone a /home/olpc/Library/makeindex.py Is there an update I have to do, or someplace where I can grab makeindex.py? -eric ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Packaging and Hello World Tutorial
On Jan 1, 2008 7:03 PM, Kent Loobey <[EMAIL PROTECTED]> wrote: > On Tuesday 01 January 2008 15:57:17 you wrote: > > I was trying a modification of the Hello World tutorial > > What is the URL to the "Hello World tutorial" of which you speak? > > Thanks. > Started with: http://wiki.laptop.org/go/Sugar_Activity_Tutorial and then tried the differences present in: http://wiki.laptop.org/go/Creating_an_activity but the key seems to be the: find ./ | sed 's,^./,YourActivityName.activity/,g' > MANIFEST The inclusion of YourActivityName.activity seems to be the key problem. -eric ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Packaging and Hello World Tutorial
I was trying a modification of the Hello World tutorial to package an application with a bunch of additional files (essentially the python acts as a launcher at the moment). In any case, when I follow the hello world tutorial instructions to create the MANIFEST and run setup.py, it complains about not being able to find the base component of the path as it starts to process the MANIFEST list as if its 'cwd' is the wrong directory. When I replace the step which builds the MANIFEST from the find command with a much more simple find command (find ./ > MANIFEST), things seem to work, but it really doesn't like sub-directories (particularly empty ones). So - what's the suggested path here? Should I just manually create the package and zip it externally? Is there some easier path to what I'm trying to accomplish? -eric ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New Project: inferno-olpc
1. Project name : inferno-olpc 2. Existing website, if any : http://www.vitanuova.com/inferno 3. One-line description : Customized launcher and environment for running a hosted Inferno instance. 4. Longer description : Inferno is a virtual-machine based distributed operating system environment originally developed at Bell Labs. : Adding Inferno to OLPC will create yet another environment for development and exploration as well as a number : of new applications. Inferno can be run today from the shell, but the goal of this project is to optimize Inferno for : the OLPC in order to better integrate it with the rest of the environment. 5. URLs of similar projects : http://gsoc.cat-v.org/projects/OLP9C/ 6. Committer list Please list the maintainer (lead developer) as the first entry. Only list developers who need to be given accounts so that they can commit to your project's code repository, or push their own. There is no need to list non-committer developers. Username Full name SSH2 key URLE-mail - -- #1 ericvh Eric Van Hensbergen [EMAIL PROTECTED] #2 #3 ... If any developers don't have their SSH2 keys on the web, please attach them to the application e-mail. 7. Preferred development model [] Central tree. Every developer can push his changes directly to the project's git tree. This is the standard model that will be familiar to CVS and Subversion users, and that tends to work well for most projects. [X] Maintainer-owned tree. Every developer creates his own git tree, or multiple git trees. He periodically asks the maintainer to look at one or more of these trees, and merge changes into the maintainer-owned, "main" tree. This is the model used by the Linux kernel, and is well-suited to projects wishing to maintain a tighter control on code entering the main tree. If you choose the maintainer-owned tree model, but wish to set up some shared trees where all of your project's committers can commit directly, as might be the case with a "discussion" tree, or a tree for an individual feature, you may send us such a request by e-mail, and we will set up the tree for you. 8. Set up a project mailing list: [X] Yes, named after our project name [ ] Yes, named __ [] No When your project is just getting off the ground, we suggest you eschew a separate mailing list and instead keep discussion about your project on the main OLPC development list. This will give you more input and potentially attract more developers to your project; when the volume of messages related to your project reaches some critical mass, we can trivially create a separate mailing list for you. If you need multiple lists, let us know. We discourage having many mailing lists for smaller projects, as this tends to stunt the growth of your project community. You can always add more lists later. 9. Commit notifications [X] Notification of commits to the main tree should be e-mailed to the list we chose to create above [ ] A separate mailing list, -git, should be created for commit notifications [] No commit notifications, please 10. Shell accounts As a general rule, we don't provide shell accounts to developers unless there's a demonstrated need. If you have one, please explain here, and list the usernames of the committers above needing shell access. 11. Translation [X] Set up the laptop.org Pootle server to allow translation commits to be made [ ] Translation arrangements have already been made at ___ 12. Notes/comments: id_rsa.pub Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel