8000 rename to 'SDL2' · Issue #34 · andrewrk/SDL · GitHub
[go: up one dir, main page]

Skip to content

rename to 'SDL2' #34

Open
Open

Description

@kristoff-it

To lower the amount of confusion between this repo and the ayc/SDL3 repo, I'd like to rename this repo to SDL2. This won't break CI for existing users because GitHub keeps the redirect for as long as we don't override it.

If anybody has reason to push against this idea, please post here. I'll wait a couple of days and then push the change if nobody raises a complatint.

Activity

  1. jayschwa commented on Jun 30, 2026

    @jayschwa

    The SDL_image and SDL_ttf repos have v3 on the main branch and v2 on the v2 branch. I'd be in favor of doing that here too. v2 can be created off main, and then the SDL3 contents can be force pushed onto the main branch.

  2. jayschwa commented on Jun 30, 2026

    @jayschwa

    (That's also the same strategy upstream uses.)

  3. kristoff-it commented on Jun 30, 2026

    @kristoff-it
    Author

    Thank you for chiming in, would you be open to the idea of doing what you describe but to the SDL3 repo?

    Meaning we create a v2 branch in the SDL3 repo with the contents of this repo, and then we delete this repo and rename SDL3 to SDL. I would of course give you write rights to that repo same as this one.

    I'm suggesting this so that the repo stops being a fork of the upstream repo (GH doesn't let me leave the fork network with this repo).

  • jayschwa commented on Jun 30, 2026

    @jayschwa

    That works too. I'm curious why the fork network matters - why do you not want it?

  • kristoff-it commented on Jun 30, 2026

    @kristoff-it
    Author

    yeah doesn't matter much, it's mainly because the v3 code uses the pristine tarball approach.

  • kristoff-it commented on Jun 30, 2026

    @kristoff-it
    Author

    @MasonRemaley are you also on board with this plan?

  • MasonRemaley commented on Jun 30, 2026

    @MasonRemaley

    This sounds good to me, though IMO we should name the branch SDL2.

    The upstream projects in libsdl-org have a branch named SDL2 that serves the same purpose, so this naming scheme is familiar. Additionally, this it removes any chance of confusion around whether v2 is v2 of the library, v2 of Zig, v2 of SDL, or something else.

  • kristoff-it commented on Jul 1, 2026

    @kristoff-it
    Author

    @jayschwa you have now write access to SDL3, ping me when you have created your branch and are ready to commit to the switch.

  • jayschwa commented on Jul 1, 2026

    @jayschwa
  • Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      No labels
      No labels

      Projects

      No projects

        Milestone

        No milestone

        Relationships

        None yet

        Development

        No branches or pull requests

        Issue actions

        0