* [gentoo-dev] last rites: app-office/hamster-time-tracker
@ 2017-12-06 22:41 Nicolas Bock
2017-12-07 8:20 ` Geaaru
0 siblings, 1 reply; 4+ messages in thread
From: Nicolas Bock @ 2017-12-06 22:41 UTC (permalink / raw
To: gentoo-dev, gentoo-dev-announce
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
# Nicolas Bock <nicolasbock@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/c3e5fb761c88fdecfd1566cac8b6836228a27cce
--
Nicolas Bock <nicolasbock@gentoo.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] last rites: app-office/hamster-time-tracker
2017-12-06 22:41 [gentoo-dev] last rites: app-office/hamster-time-tracker Nicolas Bock
@ 2017-12-07 8:20 ` Geaaru
2017-12-07 9:10 ` Jonas Stein
2017-12-07 18:18 ` Nicolas Bock
0 siblings, 2 replies; 4+ messages in thread
From: Geaaru @ 2017-12-07 8:20 UTC (permalink / raw
To: gentoo-dev; +Cc: gentoo-dev-announce
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
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.
My cent
Thanks
G.
On Dec 6, 2017 11:42 PM, "Nicolas Bock" <nicolasbock@gentoo.org> wrote:
> # Nicolas Bock <nicolasbock@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 <nicolasbock@gentoo.org>
>
[-- Attachment #2: Type: text/html, Size: 2258 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] last rites: app-office/hamster-time-tracker
2017-12-07 8:20 ` Geaaru
@ 2017-12-07 9:10 ` Jonas Stein
2017-12-07 18:18 ` Nicolas Bock
1 sibling, 0 replies; 4+ messages in thread
From: Jonas Stein @ 2017-12-07 9:10 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1.1: Type: text/plain, Size: 381 bytes --]
Dear Geaaru,
> I will try to investigate on it in the christmas holidays and see if I can
> take care of ebuild maintenance.
To me it looks like a completely new ebuild is required in that case.
Nice to hear that you want to proxy maintain it, you will find
everything on our overhauled wiki site
https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
Best,
Jonas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-dev] last rites: app-office/hamster-time-tracker
2017-12-07 8:20 ` Geaaru
2017-12-07 9:10 ` Jonas Stein
@ 2017-12-07 18:18 ` Nicolas Bock
1 sibling, 0 replies; 4+ messages in thread
From: Nicolas Bock @ 2017-12-07 18:18 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]
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" <nicolasbock@gentoo.org> wrote:
>
>> # Nicolas Bock <nicolasbock@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 <nicolasbock@gentoo.org>
>>
--
Nicolas Bock <nicolasbock@gentoo.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-12-07 18:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-06 22:41 [gentoo-dev] last rites: app-office/hamster-time-tracker Nicolas Bock
2017-12-07 8:20 ` Geaaru
2017-12-07 9:10 ` Jonas Stein
2017-12-07 18:18 ` Nicolas Bock
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox