Arch Linux User Repository

I am hesitant to have to make this change because I would feel that I would have to make it
in all the other packages I maintain!

That is the work you have to do, when you are on a public space like AUR and have to correct a mistake.

nvrs-bin /usr/share/doc/nvrs-bin/
nvrs-bin /usr/share/licenses/nvrs-bin/LICENSE

/usr/share/doc/XYZ-bin/...md files
/usr/share/doc/XYZ-git/...md files
/usr/share/licenses/XYZ-bin/LICENSE
/usr/share/licenses/XYZ-git/LICENSE

That, is a mistake.

You also make the same mistake in,

https://aur.archlinux.org/packages/viddy-bin

https://aur.archlinux.org/packages/hwatch-bin

@m040601 I just recently learned about namcap and it don´t indicate that problem!

I am hesitant to have to make this change because I would feel that I would have to make it in all the other packages I maintain!

I must have done it this way because I saw some other packeges of third parties doing the same thing!

I will read the documentation and adjust over time!

Thanks.

... You have some documentation that advises in that regards?

All the many relevant wiki pages.

https://wiki.archlinux.org/title/Arch_packaging_standards
https://wiki.archlinux.org/title/Arch_User_Repository
https://wiki.archlinux.org/title/VCS_package_guidelines
https://wiki.archlinux.org/title/PKGBUILD
https://wiki.archlinux.org/title/Makepkg
... etc

Check out how our beloved yay does it,

https://aur.archlinux.org/packages/yay
https://aur.archlinux.org/packages/yay-bin
https://aur.archlinux.org/packages/yay-git

It even supports like 20 different languages. Can you imagine the triplicated mess if you had specific names for "-bin" and "-git" ?

yay-bin /usr/share/locale/... russian ... chinese ... /LC_MESSAGES/yay.mo
yay-bin /usr/share/locale/... russian ... chinese ... /LC_MESSAGES/yay-bin.mo
yay-bin /usr/share/locale/... russian ... chinese ... /LC_MESSAGES/yay-git.mo

adamperkowski already advised you to use namcap.

In your case, since you maintain a lot of PKGBUILD I strongly recommend that you learn to use these review and automation tools.

But they are no guaranteed miracle !!! In the end you are a human and have to supervise and think carefully about things.

Specially for someone building variations like "-git" or "-bin".

Make sure to search the AUR exaustevly before submitting new ones.

Make sure you master the use of these tags,

Conflicts
Provides
Replaces

... Every other packages that I see,
...., use the folders that way 

Remember what is written at the bottom of the page,

AUR packages are user produced content. Any use of the provided files is
at your own risk.

There is nobody officially working at the AUR. There is nobody officially checking if your AUR PKGBUILDs are "correct". Also there is no automated system or computer doing that.

If somebody puts something "bad" in the AUR, it can in fact just stay simply there. Like Microsoft Windows virus living on the Internet.

The ones commenting and advising here on you PKGBUILD's are just volunteers. That just by chance got an interest in your PKGBUILD.

There will be thousands of others "doing it that wrong way" that you encounter on the AUR. Left alone, living there in silence forever.

The fact that nobody said anything, reviewed them, policed them, marked them or removed them, doesnt say that they are "good".

About people talking.

Do not trust the AUR more than you trust the Forums.

Do not trust the Forums more than you trust the Wiki.

Do not trust the Wiki more than you trust the Homepage of Archlinux.

@m040601 Every other packages that I see, inclusive others that I maintain, use the folders that way (with the full name of the package). You have some documentation that advises in that regards? Thanks

Use namcap.

@m040601 Every other packages that I see, inclusive others that I maintain, use the folders that way (with the full name of the package). You have some documentation that advises in that regards? Thanks

@Dominiquini

You still need to correct

$ pacman -Ql nvrs-bin

...
nvrs-bin /usr/share/doc/nvrs-bin/
nvrs-bin /usr/share/doc/nvrs-bin/CHANGELOG.md
nvrs-bin /usr/share/doc/nvrs-bin/CONTRIBUTING.md
nvrs-bin /usr/share/doc/nvrs-bin/README.md
........
nvrs-bin /usr/share/licenses/
nvrs-bin /usr/share/licenses/nvrs-bin/
nvrs-bin /usr/share/licenses/nvrs-bin/LICENSE
.....



To

nvrs-bin /usr/share/doc/nvrs/ nvrs-bin /usr/share/licenses/nvrs/ ```

No "-bin" there.

Hey. Thanks for creating a -bin package for nvrs. I've updated the release structure. It now packages every important file into a tarball. The package can use that now. The current download URL is:

https://github.com/adamperkowski/nvrs/releases/download/v0.1.7/nvrs-v0.1.7.tar.gz

Thanks for the "-bin" PKGBUILD. Very usefull.

You should not use,

/usr/share/doc/nvrs-bin/
/usr/share/licenses/nvrs-bin/

No "-bin". It should be,

/usr/share/doc/nvrs/
/usr/share/licenses/nvrs/

Today I learned something new. Very nice hack from you, to separately pull the "README" and " LICENSE plain text files.

url="https://github.com/${_pkgauthor}/${_pkgname}"
_urlraw="https://raw.githubusercontent.com/${_pkgauthor}/${_pkgname}/v${pkgver}"

source=("LICENSE-${pkgver}::${_urlraw}/LICENSE"
        "README-${pkgver}.md::${_urlraw}/README.md")

source_x86_64=("${url}/releases/download/v${pkgver}/${_pkgname}")

  install -Dm644 "LICENSE-${pkgver}" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
  install -Dm644 "README-${pkgver}.md" "${pkgdir}/usr/share/doc/${pkgname}/README.md"

I asked the developer to release a proper tar.gz file containing all that.

In the mean time, and if he doesnt do that.

He also has a sample configuration file "nvrs.toml" in the repo root. Essential to get started. Can you also add it ? So that it also ends up in

/usr/share/doc/nvrs/sample.nvrs.toml

Thanks in advance.