Package Details: xq 1.1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: xq
Description: Command-line XML and HTML beautifier and content extractor
Upstream URL:
Licenses: MIT
Conflicts: yq
Submitter: syui
Maintainer: grawlinson
Last Packager: grawlinson
Votes: 1
Popularity: 0.20
First Submitted: 2018-06-10 05:02 (UTC)
Last Updated: 2023-01-25 00:14 (UTC)

Latest Comments

danlamanna commented on 2022-11-16 01:33 (UTC)

Confusingly, this package conflicts with The yq package also installs a /usr/bin/xq.

eclairevoyant commented on 2022-11-15 08:19 (UTC) (edited on 2022-11-15 08:20 (UTC) by eclairevoyant)

Wouldn't cleaning up the cache every once in a while solve that issue (find $SRCDEST -name '*.gz' -exec rm '{}' \;)?

I believe there's many good reasons to not use git for packages that aren't -git packages:

  • Using a git repo increases download size. Git repos are always increasing in size and are much larger than the code itself - as an example here, the gzip file is 164 KB compared to the repo itself taking up 668 KB

  • Using git adds an extra build dep that has to be installed (especially when building in a clean chroot as is always recommended)

  • If we want to check the PKGBUILD for correctness, that requires an extra step of going to check GitHub or opening up the git repo in $SRCDEST manually and ensuring the commits and tags match

  • Git uses SHA-1 for commit hashes which are notably more likely to have collisions than the hashes used in this PKGBUILD

  • This package is so small that git itself is several orders of magnitude larger than the entire repo

And in the case of this package, I don't think a few hundred kilobytes is really going to fill up your disk space if you have git (38+ MiB) installed.

grawlinson commented on 2022-11-15 02:56 (UTC)

Less disk cache used, I'd rather have one git repo than multiple tarballs that quickly eat my disk space.

eclairevoyant commented on 2022-11-13 08:26 (UTC) (edited on 2022-11-13 08:28 (UTC) by eclairevoyant)

@pmarreck FYI not sure where you got the idea that aurweb or its packages use svn, but that hasn't been true for about 7 years. everything's git-based.

also @grawlinson why use git instead of fetching the archive ( directly?

noraj commented on 2022-09-07 17:30 (UTC)

also I will conflict with if someone add it, for example it's packaged in debian

pmarreck commented on 2022-02-16 21:54 (UTC) (edited on 2022-02-16 22:07 (UTC) by pmarreck)

If you add the following lines ahead of the "go build" command in the PKGBUILD after cd'ing to the package dir, it should at least complete, but I agree with @andykluger, just update it to build from source

go mod download
go get

It should at least install with that, but yeah, build from source pls. This utility would have just been really helpful to parse RSS feeds using jq syntax...

I can't stand Go, otherwise I'd volunteer to maintain this; if there was such a thing as a pull request and a test suite, I could have just contributed by fixing the issue and creating a PR, but Arch doesn't use Git, it uses SVN (as I'm just now discovering), sigh

oriba commented on 2021-06-01 13:30 (UTC)

This package is not just outdated (flagged as outdated since 2021-02-09), but also does not create the package.

==> Starting build()... go: missing go.sum entry; to add it: go mod download ==> ERROR: A failure occurred in build(). Aborting...

andykluger commented on 2020-02-28 16:04 (UTC)

Please, update this to build from source. It is standard practice here to explicitly name packages "<pkg>-bin" if it just pulls a built blob. Otherwise, it should build from source.

mithrial commented on 2020-01-22 19:12 (UTC)

0.3.3-1 has the wrong sha1sum