Difference between revisions of "Creating and Maintaining a Module Repository"
David Haslam (talk | contribs) m (→References: <references />) |
David Haslam (talk | contribs) (→References: # [http://www.amazon.com/s?ie=UTF8&tag=mozilla-20&index=blended&link_code=qs&field-keywords=Access%20Denied%3A%20The%20Practice%20and%20Policy%20of%20Global%20Internet%20Filtering Acc) |
||
| Line 23: | Line 23: | ||
== References == | == References == | ||
| − | + | # [http://www.amazon.com/s?ie=UTF8&tag=mozilla-20&index=blended&link_code=qs&field-keywords=Access%20Denied%3A%20The%20Practice%20and%20Policy%20of%20Global%20Internet%20Filtering Access Denied: The Practice and Policy of Global Internet Filtering (Information Revolution and Global Politics)]. | |
Revision as of 11:10, 29 November 2008
Layout of a Module repository
A module repository is an echo of the mods.d and modules area as found under any Sword module area on your system (e.g. ~/.sword) plus mods.d.tar.gz, as created by:
tar czvf mods.d.tar.gz mods.d/*
Several front ends (particularly for small devices) do require modules in a different format though, as a zipped file.
mods.d.tar.gz is a gzipped file.
Zipped files
Some of the smaller devices running a sword frontend do not have a network enabled module manager. Users of these devices need to download their modules as zipped files and unzip them in the right place - e.g. a SD card.
It is also helpful for people who have no access to direct internet connections or live in countries with monitored access to the internet to be able to download (and possibly distribute) zipped modules.
These come in three formats
- rawzip
- zip for MS Windows
- zip for Mac OSX
