Package Details: yarsync 0.2.1-2

Git Clone URL: https://aur.archlinux.org/yarsync.git (read-only, click to copy)
Package Base: yarsync
Description: Yet Another Rsync is a file synchronization and backup tool
Upstream URL: https://github.com/ynikitenko/yarsync
Keywords: backup mirroring rsync synchronization
Licenses: GPL3
Submitter: Alxe
Maintainer: ynikitenko
Last Packager: ynikitenko
Votes: 3
Popularity: 0.000003
First Submitted: 2018-04-24 11:46 (UTC)
Last Updated: 2023-05-22 10:30 (UTC)

Latest Comments

« First ‹ Previous 1 2

m040601 commented on 2023-03-13 03:23 (UTC) (edited on 2023-03-13 03:40 (UTC) by m040601)

Thank you for this curious and interesting tool. Long time fan of rsync, and now I'm testing yarsync.

Nice to see that you are both the developer and maintainer of this PKGBUILD.

Here my two comments about this PKGBUILD

  • You should remove the "man-db" from the dependencies of this PKGBUILD.
  • You should add all the README's, and .md's and docs to this PKGBUILD.

content:

1. You should remove the "man-db" from the dependencies of this PKGBUILD.

I dont understand why you put this:

depends=('python' 'man-db')

I think I've never seen a PKGBUILD with a "mandatory" dependency for "man-db". Except of course those that deal explicitally with man pages.

I assume what you want to do is to install the man page of "yarsync". So you have this.

    install -D docs/yarsync.1.gz ${pkgdir}/usr/share/man/man1/yarsync.1.gz

That is correct. That is enough. You dont have to force the user to install "man-db". Actually you should not mess with that at all.

I think you are confusing the tool to display and manage the man pages, "man-db" or "mandoc", with the man pages itself, that is, the "meat", the content, the files that get installed to /usr/share/man/xyz ... (https://wiki.archlinux.org/title/Man_page)

This is for example the damage and breakage that would be caused in my system:

:: Checking for conflicts...
:: Checking for inner conflicts...
 -> Package conflicts found:
 -> Installing man-db will remove: mandoc (man)
 -> Conflicting packages will have to be confirmed manually
[Repo Make:5]  libpipeline-1.5.7-1  man-db-2.11.2-1  python-pyproject-hooks-1.0.0-1  python-build-0.10.0-1  python-installer-0.6.0-1
[Aur:1]  yarsync-0.2-1

As you can see, if I were to install "yarsync" it would make a big mess on my system. It would force me to install a tool I dont want, "man-db", and force me to remove a tool I want "mandoc".

I my case, like everyone on the planet, I also read and have the same man pages everyone has. But the tool to read them is "man" from the package "mandoc". Not "man" from the package "man-db"

2. You should add all the README's, and .md's and docs to this PKGBUILD.

I see you have a man page. I also see that you have a very interesting README. It takes time to read, understand your points. And you have also more .md's in "docs". Things like "details" etc. And then you have the documentation online.

I dont know if these overlap or not. But I hate to install a PKGBUILD and be forced to go back online to the Internet just to read documentation.

Please make sure every thing usefull to this PKGBUILD ends up in something like, for example:

/usr/share/doc/yarsync/README
/usr/share/doc/yarsync/Advanced.md
/usr/share/doc/yarsync/Tutorial.md
/usr/share/doc/yarsync/Details.md

and

/usr/share/licenses/yarsync/LICENSE.xyz

Thanks in advance ```

ynikitenko commented on 2022-07-01 15:32 (UTC)

Hi! Just for everyone to know: from 2018 (when it was created) this was a package by Alxe (https://github.com/A-lxe/yarsync). It was not very popular, so I hope there will be no issues for other people.

I created a different package with exactly same name, so don't mess these two ones! Thanks to the author for allowing me to take this AUR name!