Age | Commit message (Collapse) | Author |
|
|
|
There are more informed choices than just using the most complex
available checksum algorithm.
The PKGBUILD instructions in the Arch Linux Wiki [1] considers sha256 as
most common sha-2 sum. As a faster alternative, md5 is recommended. The
PKGBUILD manual page [2] also considers it to be the default.
[1]: https://wiki.archlinux.org/index.php/PKGBUILD
[2]: https://www.archlinux.org/pacman/PKGBUILD.5.html
|
|
|
|
Due to blindly trusting a bad heuristic in pkgrepotools [1] at some point in
time duplicates of the packaged content slipped into the distribution
branch, as PKGBUILD and files lie side by side in the project
repository.
[1]: https://github.com/dffischer/pkgrepotools/commit/4f3debb
|
|
As the README already noted, the PKGBUILD that packages the templates
itself intentionally serves a good example on how to use them. As such,
it should be shipped out included with the documentation.
|
|
Individual configuration is taken into account by adapting the checksum
algorithm to whatever is noted in makepkg.conf.
|
|
Other packages usually depend on the package without any -git suffix.
This makes it possible to als satisfy these dependency requirements when
they target a specific version or range.
|
|
As this project does not have any releases yet, all of its version
numbers are revisions which start with the letter 'r' and thus are
regarded smaller than any number, indicating a need to update even a
current installation. Revision zero instead is in turn smaller than any
other revision and leads to the correct behaviour.
|
|
|