Package Details: bat-extras-git 2020.10.05.r1.g0df5cff-1

Git Clone URL: https://aur.archlinux.org/bat-extras-git.git (read-only, click to copy)
Package Base: bat-extras-git
Description: Bash scripts that integrate bat with various command line tools.
Upstream URL: https://github.com/eth-p/bat-extras
Licenses: MIT
Conflicts: bat-extras
Provides: bat-extras
Submitter: desbma
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 2
Popularity: 0.184987
First Submitted: 2019-11-23 16:37
Last Updated: 2020-10-04 19:46

Dependencies (8)

Required by (0)

Sources (3)

Latest Comments

1 2 Next › Last »

desbma commented on 2020-05-01 13:41

@yochananmarqos I have orphaned the package, feel free to take it over. I only use batman now among the scripts, so I'm not the best person to maintain it.

yochananmarqos commented on 2020-04-28 15:04

@desbma:

There are some missing optional dependencies:

optdepends=('ripgrep: required for batgrep script'
            'entr: optional for batwatch script'
            'ncurses: optional for batdiff script'
            'prettier: various formatting for prettybat'
            'shfmt: bash formatting for prettybat')

eth-p commented on 2020-04-21 02:54

I'm a bit late to comment here, but there's a couple things that can be done about some of the issues mentioned:

The build script does not support separating building from testing.

A little while ago, I changed how build.sh works. If you pass --no-verify as a parameter, it won't attempt to run tests on the built "bin" scripts.
For testing in a separate step, you can run ./test.sh --compiled after running the build.

This does not build without ripgrep installed.

If you only want to test specific test suites, that can be done with ./test.sh --compiled --suite batgrep. The list of valid suite names can currently be found with this command:

for suite in test/suite/*.sh; do basename "$suite" .sh; done

the authors of bat-extras explicitely recommend using the git master branch instead of a release

I'm not explicitly against using a release build, but I recommended using the git master since I haven't established a proper release cycle yet.

Git tags are now available

With the latest release, I changed the version numbers recently to be yyyy.mm.dd instead of yyyymmdd, since the previous format wasn't as clear about what it represented as I felt it should have been.


If anybody has any questions or issues about bat-extras, I would be happy to help with them. The best way is to make an issue on the GitHub repository, but I'll be trying to keep an eye out for anything that comes up here as well.

yochananmarqos commented on 2020-03-11 00:32

I won't add provides/conflicts for an hypothetical package that does not exist, especially when the authors of bat-extras explicitely recommend using the git master branch instead of a release.

That's logical, no worries.

I guess you have a varying standard regarding useless variables

I never said useless, I said unnecessary. There's no reason to use a custom variable when a predefined one is available.

However, it is of course permissable to prefix custom variables with an underscore as not to conflict with existing or future predefined variables. For more info, see Package etiquette.

I see nothing in the packaging guidelines about removing the '-git' suffix from the package name when installing the LICENSE files.

The name of the project is bat-extras no matter what package extension it has here. Therefore any files and folders should reflect that.

There's a reason the ${pkgname%-*} variable is used throughout the VCS PKGBUILD template instead of $pkgname.

desbma commented on 2020-03-10 23:46

I won't add provides/conflicts for an hypothetical package that does not exist, especially when the authors of bat-extras explicitely recommend using the git master branch instead of a release.

For the variable, this is a matter of coding style, I guess you have a varying standard regarding useless variables (see above).

I see nothing in the packaging guidelines about removing the '-git' suffix from the package name when installing the LICENSE files.

yochananmarqos commented on 2020-03-09 00:31

You're missing provides() and conflicts(). If someone should eventually submit a stable version called bat-extras, there would be issues as this package would conflict and Pacman won't know about it.

There's no reason to use unnecessary variables like $_gitname when you can use ${pkgname%-git}. There should be no directories or files installed with the -git extension, that is purely for the PKGBUILD.

See VCS package guidelines and my PKGBUILD for reference.

yochananmarqos commented on 2020-01-23 00:34

You missed the bit that removes the leading v from the pkgver, see my comment again. Also see VCS package guidelines.

yochananmarqos commented on 2020-01-21 23:48

Git tags are now available:

pkgver() {
    cd "$srcdir/${pkgname%-git}"
    git describe --long --tags | sed 's/^v//;s/\([^-]*-g\)/r\1/;s/-/./g'
}
20190117.r8.765658c

Please add git to makedepends() as well as add provides() and conflicts() arrays.

The license should also be installed.

desbma commented on 2019-11-25 13:45

@yochananmarqos Some users don't/want care about batgrep. Besides, this kind of stuff should be done in check(), so it should be checkdepends but the build script does not support separating building from testing.

yochananmarqos commented on 2019-11-25 00:59

...or you could add ripgrep to makedepends() for the check.