View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#4
Originally Posted by Venemo View Post
The policy should be as simple as this:
  • Each of the applications requiring some external files clearly must indicate this in its description
  • The apps' descriptions should contain how to obtain the external files
  • After installing such an app, a message must pop up that informs the user about it
  • The app must provide meaningful error messages if the external files are not there

These should be some little extra work from the developers, but very helpful for end users.
Well, this is pretty much what I described above The external package/launcher is IMHO a good solution for this because it does not require each and every maintainer to come up with such a solution on his/her own, i.e. it requires no actual code changes, just config file differences (if you depend on the given package and state your files, all of what you list would happen automatically). I find 'how to use this app' in the description fields too obscure, maybe even non-intuitive. I know we're using it for that now, but only because we don't have a real alternative.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following User Says Thank You to attila77 For This Useful Post: