Transfer existing app from GitHub RDNN to own domain

[meisenzahl]

Problem

Until recently, only apps with an RDNN were accepted according to the following scheme: com.github.<user>.<repository>.

However, it should be possible to transfer an already published app to its own domain.

Proposal

It should be possible to specify the new RDNN with the entry end-of-life-rebase when a reason for end-of-life is specified.

Prior Art (Optional)

Flatpak

hm, so instead of removing the old file, we need to rebuild that package with end-of-life-rebase as an argument to flatpak builder: https://docs.flatpak.org/en/latest/flatpak-command-reference.html?highlight=end-of-life-rebase

I think you need to file a new feature request against this repo where you can add end-of-life and end-of-life properties to the json file. And I'm also not sure if the Flatpak builder action supports these parameters, so we might need an upstream feature request there as well

Posted by @danrabbit in #292 (comment)

Flathub

There may come a point where an application is no longer maintained. In order to inform users at update or install time that it will no longer get updates, create flathub.json with these contents:

{
  "end-of-life": "This application is no longer maintained because..."
}

If the application has been renamed, you can additionally include end-of-life-rebase with the new ID. Recent flatpak versions will prompt user if they'd like to switch to the renamed app.

{
  "end-of-life": "The application has been renamed to...",
  "end-of-life-rebase": "the.new.appid"
}

Source: https://github.com/flathub/flathub/wiki/App-Maintenance#end-of-life

[meisenzahl]

Related pull requests:

• feat: add end-of-life support action-appcenter-review-parse#2
• flat-manager: Add 'end-of-life' and 'end-of-life-rebase' inputs flatpak/flatpak-github-actions#71
• Transfer existing app from GitHub RDNN to own domain #294