Skip to content

textadept: update to 12.9#60241

Closed
skinchangerdev wants to merge 1 commit into
void-linux:masterfrom
skinchangerdev:textadept-12.9
Closed

textadept: update to 12.9#60241
skinchangerdev wants to merge 1 commit into
void-linux:masterfrom
skinchangerdev:textadept-12.9

Conversation

@skinchangerdev

Copy link
Copy Markdown
Contributor

This PR updates Textadept to 12.9 with a significant amount of CMake black magic.

Note that this update includes significant changes, such as:

  • A switch to CMake from Unix Makefiles
  • A new QT version, which is the default (the GTK version is still available as textadept-gtk)

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, (x86_64)

@skinchangerdev

Copy link
Copy Markdown
Contributor Author

I'm going to make a PR to integrate the CMakeLists.txt changes upstream eventually (I'm tired right now)

@tranzystorekk

Copy link
Copy Markdown
Contributor

duplicate of #54629

@Anachron

Anachron commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

This is fine to be merged, I can close my PR, the package is orphaned anyway.

@skinchangerdev

Copy link
Copy Markdown
Contributor Author

This is fine to be merged, I can close my PR, the package is orphaned anyway.

Thanks, I'll get to work on this again soon. I mostly just need to fix some build issues and make a PR upstream for that CMakeLists.txt patch.

@skinchangerdev

Copy link
Copy Markdown
Contributor Author

Finally got around to working on this, very sorry that it took me so long. I've fixed the cross-build issues, and the package should be fine to merge now. Given that #54629 was closed as it was nearly stale and this PR was created, I think it's fair to reopen this PR.

@skinchangerdev

Copy link
Copy Markdown
Contributor Author

@tranzystorekk

@tranzystorekk

tranzystorekk commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

PRs can't be reopened if they were force-pushed to after being closed, you'll have to open a new PR instead

EDIT: hm, or maybe they can, github web UI is so weird

EDIT 2: nevermind, please just open a new PR

@skinchangerdev

Copy link
Copy Markdown
Contributor Author

PRs can't be reopened if they were force-pushed to after being closed, you'll have to open a new PR instead

EDIT: hm, or maybe they can, github web UI is so weird

EDIT 2: nevermind, please just open a new PR

Reopened as #61323.

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 this pull request may close these issues.

3 participants