Desktop file for MX Package Installer

[Jerry3904]

And again

Code: Select all

[Desktop Entry]
Name=MX Package Installer
Name[de]=MX Paket-Installer
Name[es]=
Name[fr]=
Name[it]=
Name[nl]=MX pakket installeerder
Name[sv]=MX Paket-installerare
Name[el]=Εγκατάσταση πακέτων του MX
Name[ru]=
Name[jp]=
Comment=Simple Package Installer
Comment[de]=einfache Paket-Installation
Comment[es]=
Comment[fr]=
Comment[it]=
Comment[nl]=eenvoudige pakket installeerder
Comment[sv]=Enkel Paket-installerare
Comment[el]=Απλή εγκατάσταση πακέτων
Comment[ru]=
Comment[jp]=
Exec=gksu mx-packageinstaller
Icon=/usr/share/pixmaps/mx/mx-packageinstaller.png
NoDisplay=false
Categories=System;
Type=Application

[fu-sen]

Japanese

Code: Select all

[Desktop Entry]
Name=MX Package Installer
Name[de]=MX Paket-Installer
Name[es]=
Name[fr]=
Name[it]=
Name[nl]=MX pakket installeerder
Name[sv]=MX Paket-installerare
Name[el]=Εγκατάσταση πακέτων του MX
Name[ru]=
Name[ja]=MX パッケージインストーラー
Comment=Simple Package Installer
Comment[de]=einfache Paket-Installation
Comment[es]=
Comment[fr]=
Comment[it]=
Comment[nl]=eenvoudige pakket installeerder
Comment[sv]=Enkel Paket-installerare
Comment[el]=Απλή εγκατάσταση πακέτων
Comment[ru]=
Comment[ja]=シンプルなパッケージインストーラー
Exec=gksu mx-packageinstaller
Icon=/usr/share/pixmaps/mx/mx-packageinstaller.png
NoDisplay=false
Categories=System;
Type=Application

[Stevo]

I think we should replace gksu in the exec lines with this

Code: Select all

Exec=su-to-root -c -X mx-packageinstaller

and the same for all our desktop files that need to launch as root. The advantage is that this does not depend on one program only, so the launcher will automatically use gksu in MX and kdesu in MEPIS, for example.

[anticapitalista]

I think we should replace gksu in the exec lines with this

Code: Select all

Exec=su-to-root -c -X mx-packageinstaller

and the same for all our desktop files that need to launch as root. The advantage is that this does not depend on one program only, so the launcher will automatically use gksu in MX and kdesu in MEPIS, for example.

Ok, but does the mx-packageinstaller work in MEPIS?

[Adrian]

I don't see why it wouldn't, the documentation will point to missing mxapps.html but other than that it should work fine.

[Stevo]

Yes, it does. We can then also remove gksu from the package's dependencies.

It's just good practice to make a package as portable as possible, with the fewest dependencies.

[Jerry3904]

If these MX apps are going to be used in M12, can we include the help document in the deb:

/usr/local/share/doc/mxapps.html

[Stevo]

If these MX apps are going to be used in M12, can we include the help document in the deb:

/usr/local/share/doc/mxapps.html

If that's the help for all the MX apps, how about we put that in its own package, mx-apps-help? Then we can have the MX apps have a "Recommends: mx-apps-help".

The Debian package build system doesn't like stuff in /usr/local, but I think I have a handle on how to override that.

[Jerry3904]

Right now "MX Apps" is in the documentation set with many cross-refs from other docs. We would also have to change all the links in the apps. Color me reluctant.

[Stevo]

I meant I can get it to install in the same /usr/local location, overriding any objections from the packaging system. That should keep the links intact.