Would like to see funpidgin in the tree. Reproducible: Always Steps to Reproduce:
Created attachment 151863 [details, diff] Patch pidgin-2.4.1.ebuild to funpidgin-2.4.1.ebuild I am not sure who the maintainer of pidgin-2.4.1.ebuild is, but this is almost a trivial addition. The final binaries for funpidgin will be renamed by next release, so the !net-im/pidgin dependency can be removed when that is out too.
the patch should be applied as a use flag. Much like the different brandings we can apply to firefox. This really doesn't need a full ebuild of it's own, imho.
If it was released as a patchset for the pidgin sources, and not an entirely different project, I would agree. However, since the binaries are going to be renamed to Carrier, I think it deserves it's own ebuild.
aside from rebranding and this text entry resizing patch are they going to do anything? are they actually doing a full fork? or are they going to pull from pidgin for a while? I'll use ice weasel as an example again, sure debian forked and did some rebranding, and probably some custom patches, but at the core it's still just firefox. now cedega is an old wine fork, and they aren't even close to the same sources, cedega forked and then went completely on it's own way. So I think it depends? are they planning to otherwise follow pidgin's code?
Carrier is going to be a GUI only fork. With each release we will include as many official changes from Pidgin as possible and as many of our own GTK related features as possible. The libpurple code will stay untouched. The binaries and directories are all being named carrier with the exception of /usr/lib/pidgin so the two can still share plugins. Hope that helps.
then perhaps an even more appropriate thing would be to split libpurple and finch into there own ebuilds and give carrier it's ebuild. Then we wouldn't have to install unecessary things.
well, currently latest version is 2.6.1 while pidgin 2.6.3 fixed some real security problems. Is this project alive? Is it possbile to separate GUI from other pidgin parts?
(In reply to comment #7) > well, currently latest version is 2.6.1 while pidgin 2.6.3 fixed some real > security problems. Is this project alive? Is it possbile to separate GUI from > other pidgin parts? > Hi, I'm currently maintaining Carrier. I'll try to get it back up to speed with upstream Pidgin soon. The GUI certainly can be separated. I don't think the build system as it is now was built for compiling for an existing libpurple (rather than one in the same source tree) but patches are welcome.
