| Summary: | net-im/kadu-2.1 is availiable | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | wojtek <wojtask9> |
| Component: | Current packages | Assignee: | Maciej Mrozowski <reavertm> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugzie, net-im |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
monolith kadu-2.1.ebuild
patch for qca and docking icon |
||
|
Description
wojtek
2015-03-04 15:42:56 UTC
@Maciej, do you need some help maintaining Kadu? Maybe Piotr can help -- he's keeping a lot of up-to-date versions in roslin. @Piotr, would you like to become proxy-maintainer for Kadu? I'm pretty sure users would love to see the new versions, and a lot of fame included! :) Created attachment 406060 [details]
monolith kadu-2.1.ebuild
Created attachment 406062 [details, diff]
patch for qca and docking icon
my kadu-2.1.ebuild is based on kadu-0.12.3.ebuild with adjusted dependencies. Kadu 2.1 needs patch for QCA and for icons in dock (http://www.kadu.im/redmine/issues/3020) Besides above issues everything is working OK on my system :) The icon patch breaks the tray icon on KDE4, so it's not a fix which can be applied universally. @Michał Górny, I'm the Kadu maintainer in roslin and the author of modular ebuilds. It's been my pet project for a while now, though nowadays I barely do any work with it except for the occasional bump and hotfix. Anyway, do you think the modular ebuilds stand a chance of being merged one day? I remember reavertm being strongly opposed to the idea just because of them being modular. Personally, I think modularity has more pros than cons, but I understand why you wouldn't want to litter the tree with two dozen new packages and some eclasses. Thanks for the ebuild, I'll take a look at it over the weekend and commit to Gentoo repository after my "QA checks". As for modular vs monolithic ebuild - I still maintain my opinion that it's not reasonable to maintain 30+ split ebuilds for kadu. kadu.eclass would have to be improved in order to actually remove some Qt dependencies related boilerplate. This is 'just' standalone instant-messenger client (a'ka "software in decline" thanks to Facebook or GoogleTalk web/mobile messengers) but cost of keywording/masking/stabilizations of the package would approach the one we have for gstreamer or even KDE. I barely have the time to maintain monolithic kadu (as you see I'm lagging with 2.x, this is due to delaying installation of Qt5...), I cannot see myself having the time to proxy for someone with 30+ packages at hand. If some other developer is willing to proxy those monolithic packages, I won't mind giving away ebuild ownership. (but I don't think you will find anyone with such amount of time at hand either) > If some other developer is willing to proxy those monolithic packages
^^^ those modular/split packages
In tree now. I had to fix some automagic deps, add missing include headers to make it compile with latest Qt5, remove some no longer used dependencies (like ayatana) or CMake options (signal handling). I omited QCA and icon patch for now until it's verified by upstream. dev-libs/injeqt I stole (with some cleanups) from roslin overlay. |