pidgin-lastfm-devel Mailing List for Pidgin Last.fm Plugin
Status: Inactive
Brought to you by:
natureshadow
Menu
▾
▴
pidgin-lastfm-devel — Development information for pidgin-lastfm
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dominik G. <nat...@gm...> - 2009-03-26 14:30:07
|
Hello, I just released v0.4a of the plugin which mainly fixes an error where users were flooded with error messages and that implements the new 2.0 Last.fm API more precisely. Please go mad testing! Cheers, Nik -- ICQ: 313-290-740 MSN: nat...@gm... Jabber: ni...@na... |
|
From: Dominik G. <nat...@gm...> - 2008-11-18 10:18:28
|
I just fired out a new version of the plugin, still written in Perl. It is a release to make wating for th rewrite easier for users and implements new features like the Last.fm 2.0 webservices (allowing more users to retrieve data) and more info sets that can be displayed. Go mad testing and packaging! |
|
From: Dominik G. <nat...@gm...> - 2008-10-30 12:44:08
|
Hi users, I'm sorry to inform you that the release of pidgin-lastfm version 0.4, which I announced for next week, has to be delayed for a while due to several bad issues. To explain this shortly: Last month, Pidgin 2.5.0 has been released to the public. While this version contained many bugfixes and improvements, the crew also chose to upgrade the Perl API in such a way that it will only work with Perl >=5.10. Well, the problem now is that until today, few Linux distributions have Perl 5.10 in their stable branches, so users have to do quite nasty stuff to their systems in order to get Perl working in Pidgin again. Windows users should be fine here as ActivePerl are, to my knowledge, providing Perl 5.10. Once Perl 5.10 goes into some distributions, we could easily let pidgin-lastfm depend on it by means of package management. However, it appears that the Pidgin crew are not only doing heavy upgrades, but also breaking part of the Perl API from time to time. The Perl API works through some strange overlay of the C API noone really understands, as datallah, experienced user and developer of the Perl part of Pidgin, once said to me on the Pidgin support channel. In version 2.5.0+, they for once decided to break the HTTP fetcher in a way that it will crash Pidgin every other time song information is retrieved ... As I am not willing to go on that way, finding workarounds and having endless discussions with the support crew and my users who get angry with their plugin not working, I am rewriting the entire codebase in C and then distributing it just like any other Pidgin plugin. This will ease things especially for the plugin users, as it does not really make any difference for me as I have to go through all this C stuff once again after laying it down a logn time ago ;) ... While we are rewriting the Pidgin Last.fm plugin, we are also adapting to the Last.fm API version 2.0, which will allow us to at last retrieve 'real' now-playing information (you know, the thing this software initially was intended to do but never did ;)) and even include some collaborative music experience stuff, like retrieving song and artist information in real-time in chats and stuff like that, let's just see what we will find ... I can't tell when the work will be done as this means a hell of a mess for developers, testers and packagers, so please be patient while we do our best at gettign a new and shiny version of the plugin out to you.Remember you can still use pidgin-lastfm version 0.3b in any Pidgin version, given that you have Perl >=5.10 installed ... Regards, Nik |
|
From: Dominik G. <nat...@gm...> - 2008-06-11 19:07:45
|
Hello users and packagers, I just released version 0.3b in the FRS. It is mostly a bug fix release, as I am not including new features before the first stable release. Everyone should test, test, test, under all conditions that occur to him or her, and report everything that looks like a bug! Regards, Nik |
|
From: Jan H. R. <in...@jh...> - 2008-05-01 10:15:11
|
On Wed, Apr 30, 2008 at 02:21:12PM +0200, Dominik George wrote: > Packagers: > > On most distributions, the path to the Pidgin plugins on x64 is > /usr/lib64/pidgin rather than just /usr/lib/pidgin. This should be > cared about when creating packages ... Hi Dominik, thanks for your mail. Since Debian is shipping an amd64 architecture I had a look at it. /usr/lib64 is a symlink to /usr/lib so the Debian package will probably work architecture independent. Thanks for the hint, though! Cheers, Hauke |
|
From: Dominik G. <nat...@gm...> - 2008-04-30 12:45:31
|
Packagers: On most distributions, the path to the Pidgin plugins on x64 is /usr/lib64/pidgin rather than just /usr/lib/pidgin. This should be cared about when creating packages ... -nik -- Hackerkey: v4sw3/4BCHJSUhw4+5ln3/4pr7OPck4ma2+3u7FLw3/4CTXm6+7l6+7DEGUi52ONetBeans/e2t5b7HOPen4+7a17s0MSr3p-1.75/-1.23g3AG (http://www.hackerkey.com) PGP-Key: 0xB5253284 |
|
From: Dominik G. <nat...@gm...> - 2008-04-29 13:15:44
|
Hello packagers (well, jhr, at least for now :-D), I renamend the top-level directory of the sources in the .tar.gz from pidgin-lastfm to pidgin-lastfm-0.3a. This was necessary for compatibility with RPM. The 0.3a will be replaced by the current version number in future releases, of course ... Regards, Nik -- Hackerkey: v4sw3/4BCHJSUhw4+5ln3/4pr7OPck4ma2+3u7FLw3/4CTXm6+7l6+7DEGUi52ONetBeans/e2t5b7HOPen4+7a17s0MSr3p-1.75/-1.23g3AG (http://www.hackerkey.com) PGP-Key: 0xB5253284 |
