Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48330 - [powerline] Please add plugins in the release package

Attached to Project: Community Packages
Opened by philanecros (philanecros) - Thursday, 25 February 2016, 02:33 GMT
Last edited by Jiachen Yang (farseerfc) - Thursday, 25 February 2016, 14:42 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Jiachen Yang (farseerfc)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Currently only vim plugin is packaged as `powerline-vim'

Please package other plugins like bash and tmux in the released version of powerline.
This task depends upon

Closed by  Jiachen Yang (farseerfc)
Thursday, 25 February 2016, 14:42 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Bindings are provided following the upstream.
Comment by Ng Oon-Ee (ngoonee) - Thursday, 25 February 2016, 05:35 GMT
Yes, please do this. Previous powerline package from AUR included zsh etc., these now crash with the updated powerline in some circumstances.
Comment by Jiachen Yang (farseerfc) - Thursday, 25 February 2016, 07:07 GMT
The vim plugin is packaged because it will be enabled by default once installed, so we need to explicitly opt-in this behavior. (The python-powerline in AUR didn't allow this)
Other plugins(bindings) are also provided. They are installed in '/usr/lib/python3.5/site-packages/powerline/bindings' from python-powerline or ' /usr/lib/python2.7/site-packages/powerline/bindings' from python2-powerline. Still to enable these plugins you need to modify your own configuration files (i.e. .tmux.conf for tmux or .zshrc for zsh). I see no point to provide a separate copy of these files in a split package. Just change the path in your config files and you are done.
Is there any benefits aside from breaking current config files (which should also not work if you install from pip)?
Comment by philanecros (philanecros) - Thursday, 25 February 2016, 08:08 GMT
Previously, the AUR packages install the bindings into '/usr/share/...'.

Referring to '/usr/share/...' seems much legit than referring to '/usr/lib/python3.5/site-packages/...' for configurations of other packages.
Comment by Jiachen Yang (farseerfc) - Thursday, 25 February 2016, 08:54 GMT
Previously the AUR packages installed (only vim/tmux/zsh) bindings into both '/usr/share/' and python site-packages. There are many more bindings provided by the upstream. And we cannot provide all these bindings in split packages because some of them (e.g. qtile/pdb/ipython) are actual python libraries and thus depend on specific python version. (And it's quite possible that some users do not have zsh/tmux/vim installed in their system, so install bindings to the folders of zsh/tmux/vim may cause confusion.)
The setup.py provided by the upstream do not install the bindings in '/usr/share', so if you install powerline from pip or git repo you will not find bindings in '/usr/share'. I want to follow upstream here.

But indeed it breaks config files now... I will update the package to print a message on install.

Loading...