On Fri, 21 Aug 2015 14:48:21 +0200, Simon Lees wrote:
On 08/21/2015 10:02 PM, Takashi Iwai wrote:
On Thu, 20 Aug 2015 18:34:36 +0200, Marguerite Su wrote:
On Fri, Aug 21, 2015 at 12:22 AM, Takashi Iwai tiwai@suse.de wrote:
Already scim and scim-anthy have been landed to openSUSE:42.
I guess we should do deletereq for them?
Omg!
I seemed to be outdated...the last update to scim happened 16 days ago...(github.com/scim-im/scim)...I'll sent scim-sunpinyin manually.
But anyway I don't think there's people still using it...
It's really up to maintainers to decide to take or not. If the maintenance of scim-* package isn't too difficult, we can keep them on Leap, of course. OTOH, if the maintenance load is significant, we should consider dropping them.
I myself have no preference about this at all. It's mostly you who has keeping them up, so if it's too much burden for you, we can drop them.
BTW, what is the way to drop a package from Leap? I tried deletereq to openSUSE:42/scim, but it failed like:
Server returned an error: HTTP Error 404: Not Found Couldn't find Package
OTOH, a deletereq to openSUSE:42:Factory-Copies/* results in:
The target project openSUSE:42:Factory-Copies is not accepting requests because: please submit to openSUSE:42 instead
thanks,
Takashi
I agree, if your a english typing person like me then enlightenment runs fine without it, if its to much effort to support then also drop it (I dropped some packages for 42 I don't feel like maintaining). I was more pointing out that some people still use it so don't drop it just on the basis that knowone uses it anymore :-)
Right, it's good to know that there are still users.
OTOH, our default IM framework has been switched to newer ones like ibus or fcitx already since openSUSE 13.1. Thus migrating to the new framework is strongly recommended in anyway. That is, we can't guarantee to keep the old stuff forever just because two people in the world are using it.
Look at another flip: one good way to avoiding this (dropping such packages) is to step up as the package maintainer. Then you'll have a control to it. This would be the best solution for all of us, really.
thanks,
Takashi