unnecessary file metadata from the manifest. This will allow more
metadata to the contents manifest in future versions if a need can be
16 KB (2,410 words) - 13:37, 28 August 2008
#REDIRECT [[Contents manifest specification]]
79 bytes (7 words) - 08:00, 27 January 2008
...s 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,
There is some confusion between Contents manifest and the activity's MANIFEST file. Could someone who understands both write the two line explanation ne
1 KB (192 words) - 16:14, 27 February 2008
#REDIRECT [[Contents manifest specification]]
45 bytes (4 words) - 16:01, 26 January 2008
#REDIRECT [[Talk:Contents manifest specification]]
50 bytes (5 words) - 16:01, 26 January 2008
#REDIRECT [[Contents manifest specification]]
45 bytes (4 words) - 08:00, 27 January 2008
#REDIRECT [[Talk:Contents manifest specification]]
50 bytes (5 words) - 08:00, 27 January 2008
...aged in a (somewhat heated) discussion of the XO upgrade model; a concrete specification will be the outcome.
...s Avahi to automatically find local machines that have newer versions of a manifest. He also put together a small web server that an XO can run in order to exp
121 KB (20,194 words) - 12:31, 1 June 2012
...ldActivity.activity/activity/activity.info</tt>). The [[Activity Bundles]] specification explain in detail the meaning of each field.
os.system("find ./ | sed 's,^./,HelloWorldActivity.activity/,g' > MANIFEST")
8 KB (1,266 words) - 12:36, 17 January 2014
:'''NOTE:''' This talk item was moved from [[Talk:Hardware specification]]
...rface (UI). Reviewing the UI docs starting to appear in this Wiki makes it manifest that the mesh nework is deeply integrated - not a mere afterthought for app
12 KB (2,017 words) - 10:30, 21 December 2008
contents (manifest for bundle contents)
...code>contents.sig</code> files themselves), as described by the [[Manifest Specification]]. The optional <code>mimetypes.xml</code> file is a [http://freedesktop.or
17 KB (2,542 words) - 01:03, 23 August 2012
According to the [[Hardware specification]] the ''Maximum altitude: -15m to 3048m (14.7 to 10.1 psia) (operating), -1
...ed for each country's language/s, but not braille. The OLPC has [[Hardware specification#Specifications|3 USB ports]] to which external (braille) keyboards may be c
125 KB (20,048 words) - 11:24, 1 June 2012
...ic bundle checker suite on uploaded collections : metadata, bundle format [manifest], links. More complex validation can be developed as needed.
The '''second part''' of the project proposes to revise the content bundle specification to reflect updates to the content bundle format. This part of the project w
10 KB (1,457 words) - 14:15, 25 January 2008
signed manifest; at the end of the rsync operation, the laptop will have
manifest and confirm the modified files in the updater's context exactly
14 KB (2,315 words) - 13:58, 6 October 2012
...loWorldActivity.activity/activity/activity.info). The [[Activity Bundles]] specification explain in detail the meaning of each field.
Create a MANIFEST (e.g. HelloWorldActivity.activity/MANIFEST), containing the list of the files to include in the package. (Note: Be su
5 KB (752 words) - 10:50, 23 September 2007
signed manifest; at the end of the rsync operation, the laptop will have
manifest and confirm the modified files in the updater's context exactly
26 KB (4,229 words) - 20:18, 9 September 2007
#REDIRECT [[Contents manifest specification]]
45 bytes (4 words) - 08:00, 27 January 2008
...d ''$b'' where ''$b'' cryptographically identifies the [[contents manifest specification|contents]] of the desired OS tree.)
8 KB (1,236 words) - 18:31, 27 August 2009
...code>contents.sig</code> files themselves), as described by the [[Manifest Specification]].
16 KB (2,437 words) - 15:09, 16 May 2008
#REDIRECT [[Contents manifest specification]]
79 bytes (7 words) - 08:00, 27 January 2008
* [[Manifest Specification]]
5 KB (640 words) - 14:26, 24 March 2008
| align=right | 15634 || [{{fullurl:Manifest Specification}} Manifest Specification] || align=right | 13635 || [{{fullurl:Emulating the XO/lang-ja}} Emulating
2 KB (264 words) - 17:49, 25 August 2007
The reponse body is a [[Canonical JSON]] [[Manifest Specification#Envelopes|envelope]] with type 'oatc-signed-resp' and version 1. The body
where the signature field is a [[Manifest Specification#Credentials|credential]] on the data field, signed with the "theft-deterren
11 KB (1,781 words) - 16:13, 1 June 2012
...of rsync and comparison of the [[contents manifest specification|contents manifest]] files, olpc-update is truly incremental, only updating what has changed w
...ublished by the update server, so it will then regenerate a local contents manifest and use that as a basis of pulling in updates.
10 KB (1,643 words) - 16:45, 28 February 2011
* Hardware specification
* Contents manifest specification
11 KB (1,107 words) - 06:17, 25 February 2008
...contents''' implements the technology described in the [[Contents manifest specification]]. It serves as the backend to [[olpc-update]].
The output contents manifest files (usually with extension <tt>.toc</tt>) are found in each [[builds|bui
625 bytes (84 words) - 11:28, 23 February 2011
...VistA Laboratory Universal Interface (UI) and LEDI HL7 Interface Standard Specification Version 1.2.
* Builds and closes a Shipping Manifest.
235 KB (33,830 words) - 10:15, 26 October 2011
