FS#11196 - [bash-completion] upstream is dead
Attached to Project:
Arch Linux
Opened by Xavier (shining) - Tuesday, 12 August 2008, 09:08 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 18 August 2009, 17:25 GMT
Opened by Xavier (shining) - Tuesday, 12 August 2008, 09:08 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 18 August 2009, 17:25 GMT
|
Details
Description:
The upstream development at http://www.caliban.org/bash/ seems to have stopped. The last release was in March 2006. there was apparently an attempt of Debian to take it over : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472468 But the alioth page seems still empty, the code was not even imported : http://alioth.debian.org/projects/bash-completion/ I also found this, but well, no comment : http://bash-completion.alioth.debian.org/ I can't even find the 20080705 version than Debian is using anywhere else than on the debian package page : http://packages.debian.org/fr/sid/bash-completion Maybe this debian source package could be used? Otherwise, in the bug report above, the last comment mentions this new project : http://fvue.nl/wiki/Bash_completion_lib http://code.google.com/p/bash-completion-lib/ That could be a better replacement, so there could be a new bash_completion_lib package, replacing and providing bash-completion? I personally don't use bash-completion, so any comments / investigation / testing from bash-completion users is welcome. |
This task depends upon
Closed by Aaron Griffin (phrakture)
Tuesday, 18 August 2009, 17:25 GMT
Reason for closing: Implemented
Additional comments about closing: New sources are used for the package in extra
Tuesday, 18 August 2009, 17:25 GMT
Reason for closing: Implemented
Additional comments about closing: New sources are used for the package in extra
It also includes nearly all the changes that were in the completion_updates.patch patch.
Attaching a pkgbuild tarball which would also fix
FS#11195EDIT: I should probably read the whole report before I ask questions.... :/
Rather more general changes, like all the ones that were in completion_updates.patch, so that is good.
Also, it is possible that the development happened on http://bash-completion.alioth.debian.org/ for a while, where there is bzr repo, and from where they could have generated their own source tarballs (like that 20080705 one) for their own use.
But that repo seems down now.
Since you say a diff looked good, +1 from me to change to the Debian version.
http://bash-completion.alioth.debian.org/ now indeed mentions a working git repo :
git clone git://git.debian.org/git/bash-completion/bash-completion.git
I had a look at gentoo ebuilds : http://gentoo-portage.com/app-shells/bash-completion
The last version seems a bit outdated, and I am not sure how they get their sources, and how modified they are, but at least they mention the same upstream project :
http://bash-completion.alioth.debian.org/
Looking at the git commits, the project seems to be quite active, I see no reason for not trying to switch to it.
Well I see one reason : using zsh and its better and official completion system :) I was already using zsh for a while when I reported this bug, and I am still a happy zsh user, so I have little interest in this bug.
But since bash is still quite the standard shell, and also the standard and default shell in Arch, it should interest many people.
PKGBUILD and x86_64 package for the git snapshot based package. Would someone mind building/testing (note the mksrc function)?
lsmod is indeed in /bin and not in /sbin, but modinfo is in /sbin !
Also this can be fixed with a very basic sed line :
sed -i 's#/sbin/lsmod#/bin/lsmod#' bash_completion || return 1
2) completion_updates.patch is bad imo
it prevents vim from opening archives (compressed or not). But vim is very cool for reading these :)
Attached a new PKGBUILD, which does not need any other files (archlinux_fixes.patch, completion_updates.patch and archlinux files can be dropped)
I liked the idea of the mksrc function, I improved it in mainly two ways :
1) keep the git repo once cloned, and re-use it when it exists (only do git pull)
2) use git-archive for creating the source tarball, we only need the files, not the whole git history
Let's get this in! :D
- one using stable release, for putting in extra
- one using git, following the PKGBUILD-git prototype, for putting in AUR/unsupported