On Thu, Dec 07, 2017 at 09:20:43AM +0100, Geaaru wrote:
Hi, I'm not sure that is correct to reply to this thread, sorry if not.I currently use hamster and yes master tree is unmaintained but scenario is difficult for this package. From old tree are been created different fork: * one that split module in different modules (hamster-lib, hamster-gtk, hamster-dbus,etc) * one that rebuild module on ruby * if I remember correctly one that continue python implementation But, it isn't so clear at least for me, what is the best fork or stable (I currently use old implememtation). So, I think that could be a choice try to identify a more stable fork and move ebuild to this new implementation (maybe with a rename of the package) and move ebuild to proxy-maintainer group. I will try to investigate on it in the christmas holidays and see if I can take care of ebuild maintenance.
Hi Geaaru, 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. Thanks, Nick
My cent Thanks G. On Dec 6, 2017 11:42 PM, "Nicolas Bock" <nicolasb...@gentoo.org> wrote:# Nicolas Bock <nicolasb...@gentoo.org> (6 Dec 2017) # Development has ceased, the last commit to the upstream repository was # on 16 July 2016 with a note stating that its status is unmaintained [1]. # See also Bug 640034. # # [1] https://github.com/projecthamster/hamster/commit/c3e5fb761c8 8fdecfd1566cac8b6836228a27cce -- Nicolas Bock <nicolasb...@gentoo.org>
-- Nicolas Bock <nicolasb...@gentoo.org>
signature.asc
Description: PGP signature
