Skip to content

Change project name to enable Debian packaging #305

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

Merged
merged 6 commits into from
Aug 9, 2025
Merged

Change project name to enable Debian packaging #305

merged 6 commits into from
Aug 9, 2025

Conversation

walles
Copy link
Owner

@walles walles commented Aug 9, 2025

Rename to moor.

Enables #137. Fixes #143.

I want to have moor in Debian (thereby getting into all the Debian derivative distros as well, Ubuntu and others).

Unfortunately, /usr/bin/moar is already used by another project (not named moar...), and Debian policy forbids having two different packages providing binaries with the same name, even with Conflicts annotations.

I believe renaming is the quickest way into Debian, and being in Debian is more important than retaining the name.

Apologies for the problems I know this will cause, but I believe this is a long term good decision.

@walles walles changed the title johan/moor Change project name to enable Debian packaging Aug 9, 2025
@walles walles merged commit ff72f13 into master Aug 9, 2025
2 checks passed
walles added a commit to walles/homebrew-core that referenced this pull request Aug 9, 2025
This change bumps to the new GitHub repo, new binary and installs a
"moar" migration script for existing users.

Background: walles/moor#305
walles added a commit to walles/homebrew-core that referenced this pull request Aug 9, 2025
This change bumps to the new GitHub repo, new binary and installs a
"moar" migration script for existing users.

Background: walles/moor#305
walles added a commit to walles/homebrew-core that referenced this pull request Aug 9, 2025
This change bumps to the new GitHub repo, new binary and installs a
"moar" migration script for existing users.

Background: walles/moor#305
walles added a commit to walles/homebrew-core that referenced this pull request Aug 9, 2025
This change bumps to the new GitHub repo, new binary and installs a
"moar" migration script for existing users.

Background: walles/moor#305
walles added a commit to walles/homebrew-core that referenced this pull request Aug 9, 2025
This change bumps to the new GitHub repo, new binary and installs a
"moar" migration script for existing users.

Background: walles/moor#305
walles added a commit to walles/homebrew-core that referenced this pull request Aug 10, 2025
This change bumps to the new GitHub repo, new binary and installs a
"moar" migration script for existing users.

Background: walles/moor#305
tmeijn pushed a commit to tmeijn/dotfiles that referenced this pull request Aug 12, 2025
⚠️ **CAUTION: this is a major update, indicating a breaking change!** ⚠️

This MR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [go:github.com/walles/moar](https://github.com/walles/moar) | `1.33.0` -> `2.0.3` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fwalles%2fmoar/v2.0.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fwalles%2fmoar/v2.0.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fwalles%2fmoar/v1.33.0/v2.0.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fwalles%2fmoar/v1.33.0/v2.0.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |

MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot).

**Proposed changes to behavior should be submitted there as MRs.**

---

### Release Notes

<details>
<summary>walles/moar (go:github.com/walles/moar)</summary>

### [`v2.0.3`](https://github.com/walles/moor/releases/tag/v2.0.3): : Correct go module setup after bumping to v2.0.0

[Compare Source](walles/moor@v2.0.2...v2.0.3)

On the v2 release and renaming to moor:
https://github.com/walles/moor/releases/tag/v2.0.0

### [`v2.0.2`](https://github.com/walles/moor/releases/tag/v2.0.2): : Improve migration script message

[Compare Source](walles/moor@v2.0.1...v2.0.2)

Ref: https://github.com/walles/moor/releases/tag/v2.0.0

### [`v2.0.1`](https://github.com/walles/moor/releases/tag/v2.0.1): : Add migration helper script

[Compare Source](walles/moor@v2.0.0...v2.0.1)

Packagers can install scripts/moar next to the moor binary to help
existing users migrate to moor.

No user visible changes, binaries should be identical to v2.0.0.

### [`v2.0.0`](https://github.com/walles/moor/releases/tag/v2.0.0): : Rename to moor

[Compare Source](walles/moor@v1.33.0...v2.0.0)

Except for the rename, this release introduces a tested and stable API
for people who want to embed moor in their applications:

https://github.com/walles/moor?tab=readme-ov-file#embedding

For details on the rename, see this MR:
walles/moor#305

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this MR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box

---

This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS42MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNjEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
walles added a commit to walles/chroma that referenced this pull request Aug 12, 2025
Ref: walles/moor#305

The old GitHub project was renamed, and now redirects to the new one, so
if you want to verify this is the same project, go to the old project
and you will be redirected:

walles/moor#305
walles added a commit to walles/ugrep that referenced this pull request Aug 12, 2025
Keeping the old name for backwards compatibility.

Ref: walles/moor#305

The old GitHub project was renamed, and now redirects to the new one, so
if you want to verify this is the same project, go to the old project
and you will be redirected:

`https://github.com/walles/moar/pull/305`
walles added a commit to walles/px that referenced this pull request Aug 12, 2025
walles added a commit to walles/riff that referenced this pull request Aug 12, 2025
walles added a commit to walles/NosoData-Go that referenced this pull request Aug 13, 2025
moar was renamed to moor:
walles/moor#305

As part of that change, a new stable public API was added.

This change bumps the pager API to moor v2.

I dropped the ShouldFormat setting, because that happens only for JSON
input. There should be no visible change.

I also dropped picking the style. That's done automatically based on
the terminal background color. For dark terminal backgrounds, "native"
is the default, so there should be no visible change.
piger added a commit to piger/Preferences that referenced this pull request Aug 16, 2025
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.

Name conflicts with MoarVM
1 participant