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

bookworm: fixing the executable name #85150

Closed

Conversation

snicket2100
Copy link
Contributor

Motivation for this change

the executable name used to be com.github.babluboy.bookworm. this commit changes it to just bookworm, seems cleaner this way.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

the executable name used to be 'com.github.babluboy.bookworm',
this commit changes it to just 'bookworm'.

# this changes the executable name
# from 'com.github.babluboy.bookworm' to 'bookworm'
sed -i "s/ meson.project_name(),/ 'bookworm',/g" meson.build;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather make a symlink after installation. Other packages might depend on this executable to be available.

@worldofpeace
Copy link
Contributor

Apps curated in the elementary OS ecosystem have their binary's RDDN for a reason, no namespace collisions. These are graphical applications, so launching them via executable manually with a convenient name isn't that important. I'd much rather communicate to the projects that the meson build system should create a convenience symlink.
For now, any kind of alias a user could setup in their shell would help.

@worldofpeace
Copy link
Contributor

Because of that I'm inclined to close this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants