1 |
On Thu, Dec 07, 2017 at 09:20:43AM +0100, Geaaru wrote: |
2 |
>Hi, |
3 |
>I'm not sure that is correct to reply to this thread, sorry if not. |
4 |
> |
5 |
>I currently use hamster and yes master tree is unmaintained but scenario is |
6 |
>difficult for this package. From old tree are been created different fork: |
7 |
>* one that split module in different modules (hamster-lib, hamster-gtk, |
8 |
>hamster-dbus,etc) |
9 |
>* one that rebuild module on ruby |
10 |
>* if I remember correctly one that continue python implementation |
11 |
> |
12 |
>But, it isn't so clear at least for me, what is the best fork or stable (I |
13 |
>currently use old implememtation). |
14 |
>So, I think that could be a choice try to identify a more stable fork and |
15 |
>move ebuild to this new implementation (maybe with a rename of the package) |
16 |
>and move ebuild to proxy-maintainer group. |
17 |
> |
18 |
>I will try to investigate on it in the christmas holidays and see if I can |
19 |
>take care of ebuild maintenance. |
20 |
|
21 |
Hi Geaaru, |
22 |
|
23 |
yes, you raise good points here and I found what's going on upstream pretty confusing too :) I really appreciate you wanting to investigate this further. We can help you or work with you to create a new package in case you need it. |
24 |
|
25 |
Thanks, |
26 |
|
27 |
Nick |
28 |
|
29 |
>My cent |
30 |
> |
31 |
>Thanks |
32 |
>G. |
33 |
> |
34 |
>On Dec 6, 2017 11:42 PM, "Nicolas Bock" <nicolasbock@g.o> wrote: |
35 |
> |
36 |
>> # Nicolas Bock <nicolasbock@g.o> (6 Dec 2017) |
37 |
>> # Development has ceased, the last commit to the upstream repository was |
38 |
>> # on 16 July 2016 with a note stating that its status is unmaintained [1]. |
39 |
>> # See also Bug 640034. |
40 |
>> # |
41 |
>> # [1] https://github.com/projecthamster/hamster/commit/c3e5fb761c8 |
42 |
>> 8fdecfd1566cac8b6836228a27cce |
43 |
>> |
44 |
>> -- |
45 |
>> Nicolas Bock <nicolasbock@g.o> |
46 |
>> |
47 |
|
48 |
-- |
49 |
Nicolas Bock <nicolasbock@g.o> |