Package Details: nasc 0.7.5-1

Git Clone URL: (read-only, click to copy)
Package Base: nasc
Description: Do maths like a normal person.
Upstream URL:
Licenses: GPL3
Conflicts: nasc-bzr, nasc-git
Submitter: aperez
Maintainer: aperez
Last Packager: aperez
Votes: 6
Popularity: 0.26
First Submitted: 2018-03-21 12:50
Last Updated: 2020-08-29 21:00

Latest Comments

caleb commented on 2020-08-31 07:32

Renaming the binary does not achieve any practical goal

Sure it does. It would bean I can launch it from the CLI or my desktop UI's launcher by typing in something sensible and expected. Reverse domain names as /usr/bin entries is nonsense.

Even the upstream started out doing something sensible and only switched to the RDNN scheme because their primary distribution channel is Elementary OS's AppCenter and it uses RDNN for all desktop apps. Their entire user model is heavily mouse/menu driven though so they don't care about the things Arch Linux users are likely to care about. I want to be able to launch an app under the sensible name that the pkgname and even upstream project repository are sensible enough to use: nasc.

I don't see why Arch Packaging should be held to doing silly things like this just because some other OS packaging scheme calls for them.

Alexmaras commented on 2020-08-13 13:52

Thanks @aperez, fair point. It's a fairly unfortunate binary name to launch, but I suppose a user can symlink if they prefer the actual app name instead of the namespaced one.

aperez commented on 2020-08-12 18:40

@Alexmaras: In general the way things are done when packaging software for Arch is avoiding modifications of the upstream software if possible. Renaming the binary does not achieve any practical goal, and would introduce differences with upstream, so I would rather not do that.

Alexmaras commented on 2020-08-11 05:50

Might be worth updating the PKGBUILD package() function to rename the binary from com.github.parnold-x.nasc to just nasc