Package Details: tealdeer 1.4.1-5

Git Clone URL: https://aur.archlinux.org/tealdeer.git (read-only, click to copy)
Package Base: tealdeer
Description: A fast tldr client in Rust.
Upstream URL: https://github.com/dbrgn/tealdeer
Licenses: MIT, Apache
Conflicts: nodejs-tldr, nodejs-tldr-git, tldr, tldr++, tldr-cpp-client, tldr-git, tldr-python-client
Provides: tldr
Submitter: heddson
Maintainer: dbrgn
Last Packager: dbrgn
Votes: 35
Popularity: 4.45
First Submitted: 2017-08-17 23:57
Last Updated: 2020-11-09 14:58

Latest Comments

hrniels commented on 2020-09-05 16:16

That's a good question. I think setting CARGO_TARGET_DIR globally makes sense, because it avoids building the same crates over and over again. Overwriting CARGO_TARGET_DIR would not allow that.

Therefore, IMO it's better to only set CARGO_TARGET_DIR if it's not already set. If you have set CARGO_TARGET_DIR and still don't want to use that for building a particular package, you could unset it before running makepkg. Or even for all packages built with makepkg by putting a shell script into /usr/local/bin/makepkg that unsets CARGO_TARGET_DIR before running /usr/bin/makepkg $@.

Edit: On the other hand, I just did some research and haven't yet found a single Rust package in AUR that actually supports my use case. Most packages just break if CARGO_TARGET_DIR is set and some set --target-dir, so that setting CARGO_TARGET_DIR has no effect. That's sad IMO, because as soon as one uses multiple Rust packages it gets pretty annoying to build the same crates over and over again. In particular, because that takes typically multiple minutes for each package. But it seems that at least currently there is not really a way to prevent that :/

dbrgn commented on 2020-09-05 12:06

@hrniels: Thanks for the note, I wasn't aware of this option. Wouldn't it be better to clear CARGO_TARGET_DIR by using env CARGO_TARGET_DIR=target cargo build --release instead? When I build an AUR package, I expect everything to happen in the build dir and would not want any data to "spread" on my file system.

hrniels commented on 2020-09-05 05:28

The first install command should use ${CARGO_TARGET_DIR:-target} instead of target, because people might have set CARGO_TARGET_DIR globally to build all crates in one place.

And to consider target-dir settings in $HOME/.cargo/config or so, you should also set CARGO_TARGET_DIR while building: export CARGO_TARGET_DIR=${CARGO_TARGET_DIR:-target}. The environment variable overrules target-dir.

dbrgn commented on 2020-09-04 20:34

@grawlinson: Ah, thanks, I meant to fix that but then forgot. It's now changed to ('x86_64' 'armv6h' 'armv7h' 'aarch64').

grawlinson commented on 2020-09-04 20:05

The architecture is incorrectly labelled any, can you please amend this to x86_64?

dbrgn commented on 2020-01-24 19:14

I took over the package from heddson (thanks for creating it!), will publish an update soon!

afontenot commented on 2020-01-17 08:27

Hey @heddson, assuming you're subscribed to these comments, can you either update tealdeer or release the package to the requester? Or if the requester doesn't want it, can you release it to me? I can keep it updated. New version has been out for months now.

dbrgn commented on 2018-02-19 08:27

Thanks for the update! I listed your package in the README :)

https://github.com/dbrgn/tealdeer/commit/5e1c739f2420fc1db9d2b2ac475692e8a9016480

dbrgn commented on 2018-02-11 00:55

Tealdeer 1.0.0 is out! https://github.com/dbrgn/tealdeer/

It includes a bash completion file. See PKGBUILD at https://aur.archlinux.org/packages/tealdeer-git/ for reference on how to install it.