Arch Linux User Repository

Also, you dont have to specifically name those "XXX-bin" or "XXX-git" folders with the "-bin" or "-git" appended. The PKGBUILD can be named "XXX-git" or "XXX-bin". The folders created dont have to have that "-bin" appended. This is already handled in the tag

This is not true for the license directory. Namcap is making a warning and the wiki says to use pkgname for the license: https://wiki.archlinux.org/title/PKGBUILD#license

I have reverted this change.

Concerning your question about the binary name, after asking for feedback on IRC, I will keep the privatebin name.

Thanks

this is good feedback, but why the patronizing and over-assertive tone ?

It will end up in /usr/share/license/pkgbuild/LICENSE

Yes, it's an error following the last pkgrel, will fix it.

Concerning the CHANGELOG.md and man page not in the initial package. Those file were not included in the tagged release. They are only in the last release from 2 weeks ago.

I'll add them in the package.

Concerning renaming the bin name, i don't want to break script or habits of people using this package.

I'll ask on irc or the mailing list for more information.

You forgot the "CHANGELOG.md" (and README.md) . They are not "fluff" or "bloat" . They are usefull. Specially the CHANGELOG.md. That's why they are shipped in the tar.gz.

@barbuk

You are not "forced" to follow neither the name of the upstream repo, neither the name upstream chooses for the binary.

That's why you did the right thing and named the PKGBUILD "privatebin-cli-bin". Doesnt matter if the repo is called just "privatebin".

I would personally have even choose to name the PKGBUILD "privatebin-go-cli-bin", and the binary "privatebin-go-cli". Because there are other privatebin CLI's on the AUR in rust, python etc. The sooner you do this renaming, the better. You are saving yourself a lot of trouble in the future. Even if you dont see or acccept it now, and think "it is a hassle" to rename or recreate the PKGBUILDs.

Now. Regarding the binary name. I will try to make my point again if I wasnt clear before.

Because it's the name of the upstream command: https://github.com/gearnode/privatebin

Yes indeed he also named the binary (command) so

gearnode/privatebin
A powerful CLI for creating and managing PrivateBin pastes with ease

The fact that "gearnode" choose to name his repo "privatebin" on github, and only mentions CLI in the description doesnt matter. It is a mistake and stupid decision by him in my opinion. Much worse even, is that he decided to name the binary simply "privatebin".

Now you, the PKGBUILD maintainer are on the AUR. You are in control. You dont have to blindly follow what the upstream repo does. And you decide how to name things according to the Archlinux conventions. For the end benefit of all Archlinux users.

If you pay attention, you'll notice this happens a lot in the AUR and even the official repos with other PKGBUILDs. Both for the PKGBUILD and for the name of the binary. Sometimes you have to add a suffix, "XXX-rs", "YYY-go", "ZZZ-microsoft-bin", "FOO-cloudflare-bin" , "BAR-fork-bin", "XYZ-without-ABC-bin" .

Because the original repo "name" or original "bin" name,

• was too short
• clashed with other tools
• is the same tool but implemented in other language
• etc

Check the Arch wiki pages with examples.

Now check the PKGBUILD or the "privatebin" tool, the web server in php, https://aur.archlinux.org/packages/privatebin . For example,

    install -Dm644 LICENSE.md "$pkgdir/usr/share/licenses/$pkgname/LICENSE"

It will end up in /usr/share/license/pkgbuild/LICENSE. What if they also had a man page called "privatebin" for that php web app ? That would end up in "//usr/share/man/man1/privatebin.1.gz" ?

Now yours,

$ pacman -Ql privatebin-cli-bin

....
privatebin-cli-bin /usr/share/licenses/privatebin/LICENSE
....
privatebin-cli-bin /usr/share/man/man1/privatebin.1.gz

Do you see and understand the mess and clashes ? If an Archlinux user want to install both the CLI and the php webapp ?

Hope I am clear. Check the wiki or ask others if you need.

I'm just wondering. Why did you decide to name the binary "/usr/bin/privatebin" instead of "/usr/bin/privatebin-cli" ?

Because it's the name of the upstream command: https://github.com/gearnode/privatebin

Thanks for the other feedback, i'll check if the pkgbuild need to be updated.

4  _binname=privatebin

$ !pacman -Ql privatebin-cli-bin

privatebin-cli-bin /usr/
privatebin-cli-bin /usr/bin/
privatebin-cli-bin /usr/bin/privatebin
privatebin-cli-bin /usr/share/
privatebin-cli-bin /usr/share/licenses/
privatebin-cli-bin /usr/share/licenses/privatebin-cli-bin/
privatebin-cli-bin /usr/share/licenses/privatebin-cli-bin/LICENSE/
privatebin-cli-bin /usr/share/licenses/privatebin-cli-bin/LICENSE/LICENSE.txt

I'm just wondering. Why did you decide to name the binary "/usr/bin/privatebin" instead of "/usr/bin/privatebin-cli" ?

It would be more consistent and less confusing.

There are many other CLI tools for the service "privatebin" on the AUR.

There is even the web php server itself, https://aur.archlinux.org/packages/privatebin

Also, you dont have to specifically name those "XXX-bin" or "XXX-git" folders with the "-bin" or "-git" appended.

/usr/share/licenses/privatebin-cli-bin/XXX

or

/usr/share/licenses/privatebin-cli-git/XXX

The PKGBUILD can be named "XXX-git" or "XXX-bin". The folders created dont have to have that "-bin" appended. This is already handled in the tag

Conflicts: XXX-git XXX-bin ttt

@barbuk

$ tar tf privatebin_Linux_x86_64.tar.gz

CHANGELOG.md
LICENSE.txt
README.md
man/privatebin-create.1
man/privatebin-show.1
man/privatebin.1
man/privatebin.conf.5
privatebin

Please make sure the "CHANGELOG.md", the "README.md" and the man pages land in

/usr/share/doc/privatebin-cli/README.md
/usr/share/doc/privatebin-cli/CHANGELOG.md
/usr/share/man/man1/privatebinXXX.1.gz
/usr/share/man/man5/privatebinXXX.1.gz

Thanks in advance.