I think i brought up this problem when the pnd system was first being introduced, but it didnt really go anywhere. I also have to admit ive been a bit lazy on instructing the user on what files are need and where. Most of the time I wrote something up quick and sweet in a readme. As a result I have seen threads/comments by confused users on what to do.

Originally I wanted a mechanism in the pxml that could contain a list of files, which the system would look for and report back to the user. (I think i still like this method)
Ive used some pnd's do their own checks (assume through scripts and zenity) and do not run until all required files are present.
Maybe something as simple as a identifier that a pnd requires data that is not included, and the user is directed where to find the details on the data.




From: Grazvydas Ignotas <notasas@gmail.com>
To: firmware-dev@openpandora.org
Sent: Tue, September 20, 2011 2:33:27 PM
Subject: [Firmware-dev] requirements element i PXML?

Hi,

this has been brought before, but maybe did not get much attention.
How about having optional <requirements> element in PXML, to list (in
free form) whatever the given program needs to work? For example,
quake would have:
<requirements>
<requirements lang="en_US">Copy the *.pak files from your game CD to
pandora/appdata/quake/whatever</requirements>
</requirements>
gpSP:
<requirements>
<requirements lang="en_US">gpSP requires BIOS file that should be
named gba_bios.bin and placed into /pandora/appdata/gpsp/
directory.</requirements>
</requirements>

This could be shown by repo, packet managers, launchers. Right now
this is expected to reside in readme, which is not shown by those for
obvious reasons, so you have to download the pnd first and search over
the readme for this info.

--
GraÅžvydas
_______________________________________________
Firmware-dev mailing list
Firmware-dev@openpandora.org
http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev