Package Details: exercism-bin 3.0.13-2

Git Clone URL: https://aur.archlinux.org/exercism-bin.git (read-only, click to copy)
Package Base: exercism-bin
Description: Command line client for exercism.io
Upstream URL: https://github.com/exercism/cli
Licenses: MIT
Conflicts: exercism
Replaces: exercism-cli
Submitter: linduxed
Maintainer: linduxed
Last Packager: linduxed
Votes: 65
Popularity: 1.09
First Submitted: 2019-07-28 13:36
Last Updated: 2019-12-25 17:45

Latest Comments

1 2 3 4 5 6 ... Next › Last »

linduxed commented on 2019-12-25 18:36

@berquist Implemented. Thanks for the recommendation!

linduxed commented on 2019-12-25 17:39

@berquist If that's the correct syntax, then yes, it should. This package used to be exercism-cli and changed to exercism-bin a commits ago.

berquist commented on 2019-12-24 14:17

Should the PKGBUILD have replaces=('exercism-cli')?

patrick96 commented on 2019-11-28 09:58

@linduxed Awesome :)

linduxed commented on 2019-11-28 02:53

Updated the package to 3.0.13. Thank you @patrick96 for your contribution!

patrick96 commented on 2019-11-20 09:28

Sure, no worries!

linduxed commented on 2019-11-20 09:11

@patrick96 Thank you for your work!

I can't have a look at this right away, but I'll get around to it either tomorrow evening or during the weekend.

patrick96 commented on 2019-11-20 07:39

Hi. I updated the PKGBUILD for this to 3.0.13 and I also switched over to the new release tarball names. You can find it here: https://gist.github.com/patrick96/80f7e9150b8be4ab524330a0763d6dc3

@linduxed feel free to pull this in ;)

The tarball also provides the license file and shell completion so I use it directly from there. And I also copy the zsh and bash completion to the proper location for completion to work out of the box.

I don't know where I should put the fish completion because I never used it so I just didn't include it.

EDIT: I now also included the fish completions after researching where to put them

NobbZ commented on 2019-09-12 07:54

Oh, yes, sorry, forgot that this is a binary package. Then patching is hard.

linduxed commented on 2019-09-12 01:43

@NobbZ: my suspicion is that this version of the package (binary that gets extracted from an archive) can not be patched. The source version of this package probably could be patched, but I have not considered what that would look like.

Regarding the upcoming changes to the package itself: I have not looked at this closely yet, and therefore don't know how to best handle this. I hope to take a look at this during one of the upcoming weekends.