Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change of domain #107

Open
neildarlow opened this issue Feb 4, 2023 · 12 comments · May be fixed by #137
Open

Change of domain #107

neildarlow opened this issue Feb 4, 2023 · 12 comments · May be fixed by #137

Comments

@neildarlow
Copy link

FreeCAD has transitioned from freecadweb.org to freecad.org (redirects are in place from freecadweb.org to freecad.org) and users are requested to use the freecad.org domain for accessing online resources. Perhaps this project should be renamed to be consistent with this change?

@hfiguiere
Copy link
Contributor

no. this is way too disruptive. because that mean freecad needs to be resubmitted and without user intervention all to workebenches and other will not be available.

@neildarlow
Copy link
Author

Didn't KiCad go through a similar transition and that was handled without user intervention?

@hfiguiere
Copy link
Contributor

I don't know I don't handle KiCAD.

@luzpaz
Copy link

luzpaz commented Feb 4, 2023

@kkremitzki heads-up

@adrianinsaval
Copy link
Collaborator

looks like kicad indeed did this, but I don't know if it didn't require user intervention for porting over settings and addons
flathub/org.kicad_pcb.KiCad#58
flathub/flathub#2041 (comment)

kicad developers preferred the use of the kicad.org domain, up until now freecad didn't have as much focus on the freecad.org domain, I mean the freecadweb.org domain still is listed in some places in the code repo.
While I too would prefer this flatpak be named org.freecad.FreeCAD I don't think it's worth screwing over existing users.

@luzpaz
Copy link

luzpaz commented Feb 4, 2023

JFYI, there is an open issue FreeCAD/FreeCAD#6415

@hfiguiere
Copy link
Contributor

it's seems that there is an automatic migration of the preferences directory so it could be made less painful than I orignally thought (it's a fact well hidden in the documentatin). The problem involve resubmitting it with a new name, and this is always friction.

@adrianinsaval
Copy link
Collaborator

I'll see about resubmitting the app, can you point me to where in the documentation the automatic migration is mentioned? What do we need to do to get that working?

@hfiguiere
Copy link
Contributor

this thing is that it is not documented.

The eol-rebase https://github.com/flathub/flathub/wiki/App-Maintenance#end-of-life

It will trigger the migration.
The code flatpak/flatpak@e17b263

@JustALawnGnome7
Copy link

JustALawnGnome7 commented Apr 24, 2024

@adrianinsaval Any progress on this? Once the app has been resubmitted under the new ID, it looks like the process for triggering an EOL rebase on this repo is a two-line change to flathub.json:

{
  "only-arches": ["x86_64"]
  "end-of-life": "The application has been renamed to org.freecad.FreeCAD.",
  "end-of-life-rebase": "org.freecad.FreeCAD"
}

Implementing the change in this way signals Flatpak to migrate user data from the old package (org.freecadweb.FreeCAD) to the new one (org.freecad.FreeCAD).

For additional information, see the following documentation for resubmitting the app and performing the EOL rebase:

https://docs.flathub.org/docs/for-app-authors/submission#how-to-submit-an-app
https://docs.flathub.org/docs/for-app-authors/maintenance/#end-of-life-rebase

@adrianinsaval
Copy link
Collaborator

we'll do the migration for the upcoming 1.0 release of freecad, in the current release we are still using org.freecadweb.FreeCAD ourselves. I guess I could submit it already just for the beta channel

@hfiguiere
Copy link
Contributor

@hfiguiere hfiguiere linked a pull request Sep 26, 2024 that will close this issue
@adrianinsaval adrianinsaval linked a pull request Sep 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants