title says all - lazarus depends on it (gtk2 support of lazarus is still buggy) but gdk-pixbuf is masked to be removed. would be good to leave it in if possible. Besides: Why is it planned to remove it at all as long as there is no ("real") problem and a maintainer?
That's the problem: there's no maintainer. If the lazarus maintainers want to maintain gdk-pixbuf, that's fine; until someone steps up, it goes.
This package is also in the mask.
To get it straight: i do not intend to discuss this - i do only want to understand it. Why is there a real "maintainer" needed at all, as gtk1 doesnt change any more (does it?) and there shouldnt really be serious work to do? If i am wrong with this, please tell me why. I'll try to get a working lazarus ebuild which depends on gtk2 instead, if that one wouldnt per se be on the mask list also.
(In reply to comment #3) > Why is there a real "maintainer" needed at all, as gtk1 doesnt change any more > (does it?) and there shouldnt really be serious work to do? If i am wrong with > this, please tell me why. There are issues to solve almost each time the toolchain upgrades, sometimes when its deps upgrade, and so on. And as there is no upstream maintainer (the version has been deprecated for many many years and unsupported for years over at upstream, as GdkPixbuf inside the gtk+ package is supposed to be used now), essentially by having it in the tree and having to solve all the problems ourselves, we become the "upstream" maintainers. We don't have the time to maintain 7 years old obsolete code in favour of present technology of which there is lots to maintain as is, but if someone else does... by all means > I'll try to get a working lazarus ebuild which depends on gtk2 instead, That would be great for any lazarus users! > if that one wouldnt per se be on the mask list also. gtk2 isn't going anywhere (neither is gtk1 at this point yet - for later other people have stepped up to continue maintaining gtk1). I can't speak on behalf of lang-misc herd with regards to how maintained, both upstream and distro-side, lazarus itself is.
Thanks. Didnt know there were that much problems with it. This explains everything. Lazarus is maintained by upstream. GTK2 support is still a bit buggy but useable, QT4 (not 3) support is in development and will be useable in mid '07 if everything goes on this way.
Just noticed Hanno Boeck fixed the ebuild yesterday yet - even better :-)
