Package Details: hledger-utils-git 1.12.1.r11.g209cd20-1

Git Clone URL: (read-only, click to copy)
Package Base: hledger-utils-git
Description: Utilities extending the hledger plaintextaccounting tool
Upstream URL:
Keywords: python,hledger,plaintextaccounting
Licenses: GPL
Conflicts: hledger-utils
Provides: hledger-utils
Replaces: python-hledger-utils-git
Submitter: alerque
Maintainer: alerque (nobodyinperson)
Last Packager: alerque
Votes: 0
Popularity: 0.000000
First Submitted: 2023-02-17 11:05 (UTC)
Last Updated: 2024-03-26 10:10 (UTC)

Latest Comments

alerque commented on 2023-02-23 13:37 (UTC)

Yes it is tooling and will inhibit other tooling configuration because Git finds the nearest config file. Having it in a repo blocks Git configuration being applied from parent repositories (such as aurpublish which keeps projects in subtrees) or parent directories. If you keep all your AUR checkouts in a directory with a .gitignore there you can take care of it to your liking across all projects at once without disturbing other workflows. As an example having the wildcard things like you were trying to put will block tooling that tries to add patches to the repository if every needed.

nobodyinperson commented on 2023-02-23 13:20 (UTC)

Hm, is a .gitignore really „tooling”? 🤔 It's just to ignore the build files so git status correctly only reports what changed. I don't really see how a .gitignore would prevent somebody from using their workflow. Except when that workflow would actually want to list the .gitignore'd content with git ls-files, but they would've git cloned the repo anyway, so it would have been a submodule...

alerque commented on 2023-02-23 13:15 (UTC)

Please don't put .gitignore or other build tooling in AUR package trees. Lots of existing tooling (including AUR helpers, and dev tools like aurpublish) put these Git repos inside a parent folder with tooling and configs. Including your personal workflow stuff in the repo inhibits others from being able to use their workflows.

nobodyinperson commented on 2023-02-15 15:55 (UTC)

Thanks @alerque, I went throught the Wiki and addressed some of the issues so that at least namcap is happy. I also made you a co-maintainer, so feel free to fix further things. I wasn't aware that you should only name libraries with the prefix python-, so I guess a rename to hledger-utils-git is due... I now at least added provides=(hledger-utils).

alerque commented on 2023-02-15 12:38 (UTC)

Thanks for this tooling, hledger edit is a great addition to my workflow. This PKGBUILD however needs a bit of work, there are quite a few issues with it in relation to the Arch Linux packaging guidelines. I actually just posted a hledger-utils package based on the stable tag that also addresses a lot of the packaging issues. Would you be interested in adding me as a co-maintainer here, or would you like me to post a patch to apply to this, or would an list of things to fix be better for you?