[Pkg-crosswire-devel] Obtaining package metadata (was: Automated Sword module packaging: it works)

Jonathan Marsden jmarsden at fastmail.fm
Mon Jan 26 12:48:31 GMT 2009


Jonathan Morgan wrote:

> On Mon, Jan 26, 2009 at 10:28 PM, Jonathan Marsden <jmarsden at fastmail.fm> wrote:

>> ...  The Crosswire archive does not seem to have an obvious way to
>> download just the metadata (just the *.conf files), so one can then
>> download only the Public Domain modules... so the script downloads
>> all of them, but then only builds the PD ones.  If there is a
>> better way to do this, please let me know.

> The install manager works from FTP repositories, and will download
> conf files only to show you what is available (in general, anyway).
> There is a command line install manager tool, installmgr, and it looks
> like installmgr -rl (list remote sources) will give you what you want.
>  I'm afraid I can't get mine to spit out a usage message, so I'm
> working from the source code here, but it looks like that is what it
> does, and it would I assume only get the .conf files (in fact, some
> repos are set up to have all the conf files in one tarball, meaning
> only one download).

Thanks!  Nice idea, and it nearly works :)  Doing

  installmgr --help

worked for me, and then

  installmgr -init
  installmgr -r
  installmgr -rl

worked, but I get a displayed list of module names and one line
descriptions; where is it putting the other metadata, or how do I get it
to display that data (in particular, the DistributionLicense field)?
Maybe I have to read its source code to find out that??

Jonathan




More information about the Pkg-crosswire-devel mailing list