I also do not have a strong preference, but the stapler-git structure feels slightly more appropriate to me.
Search Criteria
Package Details: stapler 1.0.0-5
Package Actions
| Git Clone URL: | https://aur.archlinux.org/stapler.git (read-only, click to copy) |
|---|---|
| Package Base: | stapler |
| Description: | A small utility making use of the pypdf library to provide a (somewhat) lighter alternative to pdftk |
| Upstream URL: | https://github.com/hellerbarde/stapler |
| Licenses: | BSD-3-Clause |
| Conflicts: | stapler-git |
| Submitter: | biginoz |
| Maintainer: | fpvogel |
| Last Packager: | fpvogel |
| Votes: | 87 |
| Popularity: | 0.000000 |
| First Submitted: | 2010-08-26 17:32 (UTC) |
| Last Updated: | 2026-04-17 23:46 (UTC) |
Dependencies (4)
- python
- python-more-itertools
- python-pypdf2AUR
- python-pip (make)
Required by (0)
Sources (1)
pigmonkey commented on 2020-08-18 19:05 (UTC)
PhCl commented on 2020-08-18 18:49 (UTC)
@m040601 Hi, I adopted the project, so I can only speculate for the reasons of choosing /opt. According to https://wiki.archlinux.org/index.php/Arch_package_guidelines#Directories, /opt should be used for "Large self-contained packages".
It is not large, but arguably self-contained. Or is it a use case to use the library, not just the executable? (I only use the /usr/bin/stapler executable.)
I don't have a strong opinion for either way. As m040601 pointed out, the stapler-git shows how it can be done, so it should not be hard. If it is a better structure, I can change it.
m040601 commented on 2020-08-16 11:10 (UTC) (edited on 2020-08-16 11:16 (UTC) by m040601)
Why does it install to /opt ?
$ pacman -Ql stapler
stapler /opt/
stapler /opt/stapler/
stapler /opt/stapler/CONTRIBUTORS
stapler /opt/stapler/LICENSE
stapler /opt/stapler/MANIFEST.in
stapler /opt/stapler/README.rst
stapler /opt/stapler/TODO
stapler /opt/stapler/poetry.lock
stapler /opt/stapler/pyproject.toml
stapler /opt/stapler/staplelib/
stapler /opt/stapler/staplelib/__init__.py
stapler /opt/stapler/staplelib/commands.py
stapler /opt/stapler/staplelib/iohelper.py
stapler /opt/stapler/staplelib/stapler.py
stapler /opt/stapler/staplelib/testfiles/
stapler /opt/stapler/staplelib/testfiles/1page.pdf
stapler /opt/stapler/staplelib/testfiles/5page.pdf
stapler /opt/stapler/staplelib/tests.py
stapler /opt/stapler/stapler
stapler /opt/stapler/tox.ini
stapler /usr/
stapler /usr/bin/
stapler /usr/bin/stapler
staple-git doesnt do this, https://aur.archlinux.org/packages/stapler-git Everything goes nicely into /usr/bin, /usr/share, /usr/lib/python..
PhCl commented on 2020-03-10 21:56 (UTC)
@Storm You're right! Thanks, I added it.
Storm commented on 2020-03-09 22:45 (UTC)
Seems like it's also missing a dep to "more-itertools" (available in community).
PhCl commented on 2020-01-17 00:31 (UTC)
@cg505 Thanks, I added git.
cg505 commented on 2020-01-17 00:11 (UTC)
@PhCl Please add git as a makedepends.
PhCl commented on 2020-01-12 16:20 (UTC)
As there is no official release, I changed it now to the last Git tag (master from Dec 15 2019), so Python 2 support is no longer needed. If there is a new release, that hack should be reverted.
In my quick test, the master version works but I cannot claim that I tested all paths.
oriba commented on 2019-12-03 11:11 (UTC)
@m040601, ok. You might start with a list of needed minimal features...
m040601 commented on 2019-12-03 08:52 (UTC) (edited on 2019-12-03 08:54 (UTC) by m040601)
@PhcI
Thanks for your work and attention to this issue.
.......QUOTE: although personally I would prefer an official release......
Yes, I also agree. Went to the stapler github repo, and on a second thought, not yet 100% convinced of that project ability to release. Let's wait.
Pinned Comments
PhCl commented on 2020-12-09 17:08 (UTC)
As python 3.8 was replaced by python 3.9, you could run into the following error:
To solve it, rebuild "python-pypdf2" and then "stapler". Then the directories for Python 3.9 should exist.