Open dwaynebailey opened 15 years ago
Created attachment 460
Examples .catalog file for Virtaal
This is one that I was playing with while experimenting on Fedora.
We should check with the list of dependencies here: http://translate.sourceforge.net/wiki/virtaal/building
Then testing with a few different distros. This need not be aligned with the release schedule, but might be dependent on versions, so we'll need to think a bit about things.
How do we deal with things we recommend but that might not be available on all platforms (e.g. libtranslate not being available on some platform)?
Let's make a simple start with this (just specifying the virtaal package) and ask for feedback on the list. My current feeling is that this is only useful on distros where Virtaal is packaged, and if it is packaged, the dependencies of the package will put most things in place. The user is already likely to have fonts and spell checkers for the languages they are interested in (and we can't specify all fonts that might be useful anyway). I'm not sure I see a use case for something much more than that. Is there? I feel inclined to remove the milestone since I don't really know what important issue we are trying to solve with this.
A simple one could work. It makes it simple to make it easy for anyone to install the package on their distro as they don't need to find or think virtaal they just click on a link.
I've removed the milestone. Its not critical
PackageKit allows a .catalog file to define various packages that the package manager will then install. This would allow us to ensure that all the dependencies for Virtaal are in place, fonts, etc.
We can put this on the front page of the wiki making it easy for any user, using a distro that uses PackageKit and had Virtaal packaged, to get the right stuff.