#1 Update desktop entry to conform to XDG specification
Opened 7 years ago by bignose. Modified 7 years ago

The desktop entry for the Mullvad GUI program is not properly conformant with the current XDG specification of the desktop entry:

  • The “Encoding” key is deprecated (all desktop entries must be encoded as “utf-8”).
  • The “GenericName” key should give a generic name of the application.
  • The “Comment” key should describe the program's purpose.
  • The “Keywords” key should specify other likely search terms that should match the application.
  • The “Icon” key can omit a specific filename, and give an icon name without suffix for the type; the XDG specification gives a default algorithm that will be used to find the best matching file.

I am addressing this in the branch https://pagure.io/mullvad-client/commits/wip/issue/standardise-desktop-entry (currently WIP so could rebase at any time).

Metadata Update from @bignose:
- Issue assigned to bignose

7 years ago

Hello Ben! I'm Erik from the Mullvad team. Thank you so much for putting your time and effort into this! I'm looking into the changes you've made and will comment and merge where appropriate :)

The changes in is in the standardise-desktop-entry branch looks good! I will test it and attempt to merge it into our codebase.

I'm Erik from the Mullvad team.

Thank you for responding to these issues :-)

Thank you so much for putting your time and effort into this! I'm looking into the changes you've made and will comment and merge where appropriate :)

I would like to see the Mullvad development team publish your repository on a service like Pagure, so that we can co-ordinate these changes with the actual commits you're using. That would make merge requests easier because the repositories would have common ancestry.

If you want to contact me via email about this collaboration, ben+python@benfinney.id.au is my address.

It would indeed be very nice to be able to work on the same repository, sadly we will not work towards that with this version of the client. We are however working on a new version of the client with the hopes that it, or at least many parts of it, will be developed in a public repository.

Login to comment on this ticket.

Metadata