Package Details: stack-static 2.5.1-4

Git Clone URL: (read-only, click to copy)
Package Base: stack-static
Description: The Haskell Tool Stack (linked statically)
Upstream URL:
Licenses: custom:BSD3
Conflicts: haskell-stack, stack, stack-bin
Provides: stack=2.5.1
Replaces: haskell-stack, stack, stack-bin
Submitter: simonfxr
Maintainer: simonfxr
Last Packager: simonfxr
Votes: 32
Popularity: 0.88
First Submitted: 2017-06-30 06:04
Last Updated: 2021-01-23 21:14

Required by (63)

Sources (2)

Latest Comments

1 2 3 4 Next › Last »

brisbin33 commented on 2021-01-25 14:02

Oops, sorry about that. I didn't realize another package would do something like that.

Just FYI that zsh-completion's _stack will always be slightly worse than this since it's static, whereas stack --zsh-completion-script will be generated and so always up to date and correct.

If you don't want to handle completions here, that's fine with me. I can run these commands myself in a pacman hook on stack-static updates.

In case it's helpful, here is my $FPATH (trimmed of my own custom locations). Placing _stack in any of these will get it loaded -- it would just have to be ahead of the location zsh-completions is using, if you want it to take precedence:

% echo $FPATH | tr ':' '\n'

/usr/local/share could work?

simonfxr commented on 2021-01-23 21:19

@brianbuccola, darn, I don't know where to place it either. Some distros have the zsh/vendor-completions directory, but this not done in arch it seems. The best I can do for now is to not write any stack completion script for zsh. I guess you could place your in /usr/local/share, would that be an option?

brianbuccola commented on 2021-01-23 13:21

@simonfxr, @brisbin33, I'm getting this error now, since zsh-completions already owns _stack:

error: failed to commit transaction (conflicting files)
stack-static: /usr/share/zsh/site-functions/_stack exists in filesystem (owned by zsh-completions)
Errors occurred, no packages were upgraded.

I could remove _stack first, or --overwrite it, but I'm wondering if there's a better solution.

simonfxr commented on 2021-01-23 10:39

@brisbin33 Good idea! I updated the PKGBUILD.

brisbin33 commented on 2021-01-22 15:37

Would it be possible to get something like:

stack --bash-completion-script stack > \

stack --fish-completion-script stack > \

stack --zsh-completion-script stack > \

Added to the post install?

gesh commented on 2020-11-18 12:44

Note -- without version info in provides, makepkg will still try to replace stack-static by stack if a package has a lower bound on the stack version

fosskers commented on 2020-05-21 17:12

One important difference is that stack-static requires having a custom PGP signature registered, while this package builds as-is.

drewbarbs commented on 2020-04-15 00:02

For anyone looking for a secondary reference re: the PGP key, the github release page for Stack version v2.3.0.1 indicates that the release has been signed with the key id E17D38358F72BEF7, and Github has verified the signature:

Denommus commented on 2020-04-14 13:28

If anyone else had trouble finding a keyserver with his gpg key, it's on

Rufflewind commented on 2020-03-01 19:03

That seems to be the core difference.

Given that stack-static actually has a smaller binary than stack-bin I'm not sure there's any reason to favor this package over stack-static on x86_64.