Search Criteria
Package Details: exercism-bin 3.5.4-1
Package Actions
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 |
Provides: | exercism |
Replaces: | exercism-cli |
Submitter: | linduxed |
Maintainer: | linduxed (esskayesss) |
Last Packager: | esskayesss |
Votes: | 77 |
Popularity: | 0.121352 |
First Submitted: | 2019-07-28 13:36 (UTC) |
Last Updated: | 2024-11-20 15:23 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »
linduxed commented on 2019-09-12 01:43 (UTC)
@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.
NobbZ commented on 2019-09-07 09:30 (UTC)
Is there a way to provide a patch during building the package that will disable the
upgrade
subcommand?Perhaps leaving the update check in place and replacing the upgrade process of downloading and replacing the binary with printing out something like "A new version has been released, please check https://aur.archlinux.org/packages/exercism-bin for an updated package".
Please also be aware of the fact, that the next release of exercism will probably break this
PKGBUILD
, as the convention to name the tarballs is going to be changed in the process of enabling automatic releases.Please see https://github.com/exercism/cli/issues/700#issuecomment-529013140 for details.
linduxed commented on 2019-07-28 14:50 (UTC)
It turns out that the zsh completion sourcing problem that I had was caused by me sourcing the files in a faulty manner and a recent update of
zsh
making this faulty method no longer work.Problem was solely on my end.
linduxed commented on 2019-07-28 13:41 (UTC)
New
exercism-bin
package is up and I have submitted the request to merge this package into the-bin
package.linduxed commented on 2019-07-22 10:24 (UTC)
@Nobbz Regarding completion:
PKGBUILD
pulls the completion files according to thepkgver
, I'm guessing that it'll work out the same.PKGBUILD
to make the problem with the completion file forzsh
go away? I don't fully understand whether this situation necessitates patching thezsh
file or not.taekyung commented on 2019-07-22 07:43 (UTC)
@linduxed, @NobbZ
Maybe it is a better idea to make 'merge request' rather than 'deletion request' on this package after creating a new one, because it that way the votes and popularity will be transferred as well.
NobbZ commented on 2019-07-22 05:58 (UTC)
Yes, as far as I understand the procedure, it would be creating a new one with a different name, pushing to that with slightly altered
PKGBUILD
(name) and then deleting this one.To avoid friction, it might be a good idea to use
provides=exercism-cli
in the new one.NobbZ commented on 2019-07-22 05:51 (UTC) (edited on 2019-07-22 05:55 (UTC) by NobbZ)
The design of the
zsh
completion has been changed, but never really was tested…I'm not sure if this was before or after 3.0.11.
The old version of the completion was written in a way that
source
ing was necessary, the new version can benefit from autoloading and discovery.The file needs to be renamend to
_exercism
and copied into the$fpath
.Also, please do not download completion files from
master
, all three completion files (bash
,fish
, andzsh
) are available in the release tarball.linduxed commented on 2019-07-21 23:36 (UTC) (edited on 2019-07-22 10:15 (UTC) by linduxed)
The latest version seems to result in the following error upon loading:
/usr/share/exercism-cli/completion/exercism_completion.zsh:local:6: options: can't change type of a special parameter
Not sure if this happens to everyone or just me.
linduxed commented on 2019-07-21 20:42 (UTC)
Package has now been updated to 3.0.12.
@swalladge: This sounds like a good idea, but unfortunately I don't know the exact procedure of how to do this. There does not seem to be some menu option in the maintainer interface.
Maybe one needs to remove the package and resubmit it with a different name? This thread seems to suggest that to be the case, but it's quite old:
https://bbs.archlinux.org/viewtopic.php?id=76460
« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »