از گوشی هوشمند Samsung Galaxy ارسال شده است.
In my opinion, creating a package for a single file (with the exception
of the Dynamic Modules), is a little overkill to do.
While I can understand that this is something desirable to some, I can
see this as an 'extra annoyance' for packaging teams, here and downstream.
I'm of the opinion that Mi
I've been looking at this a bit more. As much as I understand the
motivations, it seems incredibly heavy to create an entirely separate
package just to install one small file for vim. Looking at other
packages, it seems they've made the same decision. I see very few
(four) packages that seem to cre
A separate package just for a single file seems a little bit overkill, but
I do understand. You may not want /etc/nginx but want to edit the configs.
I do this frequently and just skip the benefits of nginx.vim.
This should stay open for discussion for a while, but I'm in support of
this change.
Package: nginx-common
Version: 1.10.0-1
Severity: wishlist
Dear Maintainer,
would it make sense to ship the vim plugin files from contrib in a separate
package (e.g. vim-nginx) instead of nginx-common. I usually edit nginx
configuration files on hosts that do not necessarily have nginx running (e
5 matches
Mail list logo
