Talk:Contents manifest specification

From OLPC

Revision as of 20:14, 27 February 2008 by CharlesMerriam (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

What use is this?

OK, the Activity_bundles spec says it's required, but it's a complicated gibberish format, without any tools to generate it. Is this just a useless paper spec? Do applications *actually* have to include a manifest, sign it, etc? Until there are real tools for anybody to easily make one, my app isn't gonna have one...

Let's go back to RPM, or preferably Deb. This not-invented-here packaging system is just painful.

User:Gnu

Tools are at http://dev.laptop.org/git?p=users/cscott/olpc-contents and they are installed on every XO. You shouldn't have to understand the details of the format; an appropriate invocation of olpc-contents-create will be performed by the .xo building tools.
CScott 13:47, 6 December 2007 (EST)


lumpy_ from #olpc-devel just pointed out to me that we more-or-less reimplemented BSD's mtree(8). --Michael Stone 02:35, 8 February 2008 (EST)

Agree with confusion...

There is some confusion between Contents manifest and the activity's MANIFEST file. Could someone who understands both write the two line explanation near the top of the article? thank you. CharlesMerriam 15:14, 27 February 2008 (EST)

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox