Le Sun, Nov 25, 2007 at 05:58:20PM +0100, Andreas Tille a écrit : > I would like to hear some explanation for > > Autogenerate our .menu files from .desktop files > > What is the sense of this and why do you think this is a specific > Debian-Med goal?
Hi Andreas, we have written a few .desktop files: sorbet【packages-med】$ find . -name *desktop | grep trunk/debian/ ./treeviewx/trunk/debian/treeviewx.desktop ./perlprimer/trunk/debian/perlprimer.desktop ./seaview/trunk/debian/seaview.desktop ./clustalw/trunk/debian/clustalx.desktop ./melting/trunk/debian/melting-gui.desktop ./gnumed-client/trunk/debian/gnumed-client.desktop ./njplot/trunk/debian/unrooted.desktop ./njplot/trunk/debian/njplot.desktop ./mummer/trunk/debian/mummer.desktop ./ballview/trunk/debian/ballview.desktop For all of them there is also a .menu file. Since the information content of the .desktop files is higher than .menu files, we can consider augenerating the .menu files from them. The Debian KDE team already does this conversion and have a script for this. In their case, the .desktop files come from upstream, but it could become the case for us as well: I hope that we can push a few of our .desktop files upstream. In summary, the benefit for us would be to factorize the information of 20 files into 10 files. I admit that it will not change things so much, but well…, this is brainstorming ;) Have a nice day, -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
