pidgin uploaded to unstable

[Benjamin Seidenberg]

Martin-Éric Racine wrote:
 > It seems to work well (it even builds against Etch, after building
 > Pidgin against Etch). Lovely! :)

Glad to hear it

 > However, I notice that you are including *.la files in the binary
 > package. These should be omitted.

Noted.

 >
 > Also, why deviate from the established practice of naming plugins
 > pidgin-pluginname? Did this rename come from upstream?

Yes.

I think this is because some of them can be used with whatever the 
gaim-text replacement is called.

 >
 > Then, some plugins install in /usr/lib/purple-2 and others in
 > /usr/lib/pidgin instead. Is this intentional?


Upstream's decisions - see above - I think it's for gtk plugins vs. for 
any libpurple based application.

 >
 > On 5/26/07, Benjamin Seidenberg <benjamin at debian.org> wrote:
 >> I'm almost ready to upload purple-plugin-pack (though I haven't looked
 >> at importing it into collab-maint or anything like that). I have to
 >> review the copyright info, as it's changed since I created
 >> debian/copyright. If anyone wants to provide feedback (would be much
 >> appreciated), I stuck my work at http://dlgeek.net/ppp/. Sorry for the
 >> inconvenient access.
 >>
 >> Benjamin
 >>
 >> Benjamin Seidenberg wrote:
 >> > I'm partial to that idea. I have an older version mostly-packaged, 
there
 >> > was some automatic stuff not quite right, that I believe has been 
fixed
 >> > since. I can put my work online soon, when I find the time.
 >> >
 >> >
 >> >
 >> > Martin-Éric Racine wrote:
 >> >> As the upstream for my plug-in pointed out, several of the plug-ins
 >> >> were merged in gaim-plugin-pack (ITP #353641) and have thus become
 >> >> obsolete. This might simplify the task for at least some of us, in
 >> >> that our individual packages are no longer relevant.
 >> >>
 >> >> What about co-maintaining pidgin-plugin-pack as a team, instead?
 >> >>
 >> >> On 5/7/07, Ari Pollak <ari at debian.org> wrote:
 >> >>> Hi all,
 >> >>>
 >> >>> You're getting this message if you're listed as the maintainer or an
 >> >>> uploader of a gaim plugin package.
 >> >>> Pidgin has been accepted into unstable, and I plan to upload
 >> >>> transitional dummy packages from gaim to pidgin in two weeks or 
so. This
 >> >>> means that you should be getting your separate pidgin plugin 
packages
 >> >>> uploaded ASAP, so that they have enough time to go through NEW. As a
 >> >>> quick checklist, you should be doing the following:
 >> >>> - Create a new package called pidgin-plugin, where it used to be 
called
 >> >>> gaim-plugin, with the sources separate from the gaim-plugin package.
 >> >>> - The build should be almost identical to the gaim plugin 
package, but
 >> >>> change the build-dependency from gaim-dev to pidgin-dev, and change
 >> >>> running dh_gaim to dh_pidgin.
 >> >>> - Prepare a gaim-plugin dummy package that just depends on
 >> >>> pidgin-plugin, but don't upload this until the gaim dummy 
packages are
 >> >>> uploaded. I'd be glad to upload your package at the same time as the
 >> >>> dummy gaim packages, just let me know.
 >> >>>
 >> >>> As always, if you have any questions, please let me know.
 >> >>>
 >> >>> Thanks,
 >> >>> Ari
 >> >>>
 >> >>>
 >> >>
 >> >
 >> >
 >>
 >>
 >>
 >
 >