search

sdkman / sdkman-db-migrations

Database migrations for the sdkman API
Apache License 2.0
69 stars 123 forks source link

Question: what is the recommended process for renaming a package #699

Open ezzarghili opened 1 week ago

ezzarghili commented 1 week ago

Hello,

The GCN (Graal Cloud Native) project and its tools are being renamed to GDK (Graal Dev Kit).

This has been already reflected on the website and repo, artifacts update is scheduld for next release on July 16th 2024 .

I was wondering what would be the best way to approch this in SDKMAN?

Thanks

marc0der commented 6 days ago

Hi @ezzarghili :wave:

I'm a bit confused about this. We currently host two variants of GraalVM, namely the Oracle packages (identified by graal on the CLI) and the Community Edition (identified by graalce).

Rename the existing package from GCN to GDK?

Not sure what that means. Is that on the SDKMAN website or somewhere else? We have nothing called GCN right now.

Create a PR for a new GDK package, how do we archive the old version (mark it as moved?)

The entire project is driven by dynamic data. If you are referring to the individual versions that we host, they are all in a database. Renaming these historic versions would require a data migration on our side. Also, we point to the actual binaries on the Internet, so I hope that you are not proposing renaming the actual web resources, as that would cause widespread breakage.

ezzarghili commented 2 days ago

Hi @marc0der Applogies if my initial post was not clear enough, I am talking about the tool defined in GCN not GraalVM.

We would want to only rename the package and new versions

Thank you for continous assistance