FS#6445 - gaim, libgaim, gaim-text

Attached to Project: Arch Linux
Opened by Marq Schneider (queueRAM) - Saturday, 17 February 2007, 23:57 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 02 May 2007, 18:06 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

With gaim 2.0, the developers have split the protocol network interface from the graphical user interface to produce libgaim and gaim, respectively. This means that other programs can use libgaim without requiring gaim. One example of this is gaim-text, which is a terminal-based program that one of their developers has been working on. Another example that uses libgaim, although not for Linux, is Adium, the OS X chat client. My proposal is that libgaim, gaim and gaim-text be made their own packages if not with the 2.0b series, then with the 2.0 stable release. I see other clients based on libgaim brewing and would like to not have to install gaim in order to use them. I am happy to provide PKGBUILDs if the maintainer of gaim requests them.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 02 May 2007, 18:06 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Won't splitup. Finch is included in gaim though.
Comment by Marq Schneider (queueRAM) - Sunday, 08 April 2007, 19:40 GMT
As of April 6, 2007, the gaim development team has changed the name of gaim, libgaim, and gaim-text to pidgin, libpurple, and finch, respectively. See http://gaim.sf.net or http://www.pidgin.im for more details. I would like to keep my feature request the same, but change the package names to these new ones.
Comment by Jan de Groot (JGC) - Sunday, 22 April 2007, 20:59 GMT
I don't think I'll implement this one. First, it will create two or three packages, which need to be maintained. Second, how stable is the API of libpurple? Knowing the GAIM devs, their normal workflow is to break up their source and binary code once every week, meaning there's no stability in API/ABI. I would suggest compiling against the static libraries that will come with the upcoming pidgin release, which solves the dependency on gaim, and also solves the API/ABI stability.
Comment by Marq Schneider (queueRAM) - Wednesday, 25 April 2007, 01:25 GMT
After some further thought about this and looking more in depth into how arch packages other programs, i think i am going to agree with you. Could we instead perhaps provide a finch package or include finch within the pidgin package?

Loading...