1 |
On Sat, Mar 4, 2017 at 8:37 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Sat, 4 Mar 2017 18:21:23 +0200, gevisz wrote: |
3 |
> |
4 |
|
5 |
>> So, in my portage tree currently there is one stable gvim package with |
6 |
>> version 8.0.0106 |
7 |
>> and one unstable gvim package, with version 8.0.0386. |
8 |
>> |
9 |
>> Why portage force me to unmask an unstable version of the package then? |
10 |
>> |
11 |
|
12 |
>> [ebuild U ] app-vim/gentoo-syntax-20170225 [20160530] |
13 |
>> [ebuild U ~] app-editors/gvim-8.0.0386 [8.0.0106] |
14 |
> |
15 |
> Because vim-8.0.0386 is stable and, presumably, the vim and gvim versions |
16 |
> must match. I would suggest filing a stabilisation bug for gvim, or |
17 |
|
18 |
Isn't it a bit bizarre that portage tries to force users to go |
19 |
unstable on such an exotic package as one of the two major text |
20 |
editors? |
21 |
|
22 |
This can't be good publicity for Gentoo. Yes, I know nobody is after |
23 |
that, but still... |
24 |
|
25 |
I couldn't find the name of the maintainer. Maybe different devs are |
26 |
in charge of vim and gvim? |
27 |
|
28 |
just |
29 |
> use emacs... |
30 |
|
31 |
What do[es] the maintainer[s] use? |
32 |
|
33 |
Regards |
34 |
|
35 |
Jorge Almeida |