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