Search Criteria
Package Details: mise 2024.4.8-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mise.git (read-only, click to copy) |
---|---|
Package Base: | mise |
Description: | The front-end to your dev env |
Upstream URL: | https://github.com/jdx/mise |
Licenses: | MIT |
Conflicts: | rtx, rtx-bin |
Provides: | mise |
Replaces: | rtx |
Submitter: | jdx |
Maintainer: | jdx |
Last Packager: | jdx |
Votes: | 14 |
Popularity: | 2.54 |
First Submitted: | 2024-01-02 22:54 (UTC) |
Last Updated: | 2024-04-23 01:32 (UTC) |
Dependencies (1)
- cargo (rust-nightly-binAUR, cargo-gitAUR, rustup-gitAUR, rust, rustup) (make)
Latest Comments
1 2 Next › Last »
Sacro commented on 2024-02-24 22:46 (UTC)
Fish completions should be moved to /usr/share/fish/vendor_completions.d/mise.fish
barraponto commented on 2024-02-18 12:41 (UTC)
Compilation is using a lot of memory in my machine. I mean, about 10GB+ memory on a 6-core Ryzen with 16GB available RAM. I sometimes see the compilation fail due to OOM errors.
alerque commented on 2024-01-19 22:16 (UTC)
Please only set conflicts on variant packages, and only against base package names. In other words this should not be marked as conflicts with mise-bin, only mise-bin should be marked to conflict with this. The package manager will resolve it from there including between other variant packages that don't necessarily reference each-other but to mutually conflict with the same base package name.
aorth commented on 2024-01-04 06:05 (UTC)
Thanks! The
conflicts
currently contains an illegal character (,).inverse commented on 2024-01-03 20:56 (UTC)
rtx
got rebranded tomise
how's best to redirect to https://aur.archlinux.org/packages/miseSacro commented on 2023-05-27 19:24 (UTC)
Can we have something like
in the package(), gives us completions!
aorth commented on 2023-03-24 05:47 (UTC) (edited on 2023-03-24 05:47 (UTC) by aorth)
I figured out why this doesn't build in a chroot. The PKGBUILD needs
options=('!lto')
.aorth commented on 2023-03-17 20:16 (UTC)
The PKGBUILD is missing something required to build in a clean chroot, though I don't know what. Here's the end of several hundred lines of error log:
If I build with
makepkg -Ccrs
it builds successfully. Any idea what is missing for the chroot build?jtdowney commented on 2023-02-09 04:17 (UTC)
@jdxcode it works for me on my system. Thanks
jdx commented on 2023-02-08 17:52 (UTC)
@jtdowney, that was bad cargo cult. I went through and simplified this logic. Works for me in a docker container. Let me know if it works on your end.
1 2 Next › Last »