RPMs

[Ethan Blanton]

Stu Tomlinson spake unto us the following wisdom:
> libpurple, libpurple-devel, pidgin, pidgin-devel, finch, finch-devel,
> various "optional" plugins as libpurple-<plugin> (eg. libpurple-tcl,
> libpurple-silc etc.)
> 
> Is this the way we want to go? It makes more sense to me to do this so
> people can install just the components they need, and increases the
> compatibility if we end up with 3rd party clients that don't want to
> force pidgin on people.

Provided that this is solved for individual file downloads, I have no
problem with it.  If it further inflates the number of RPMs in the
current tracker list, that's bad.  (You have to add up an awful lot of
the less popular RPMs to arrive at the number of downloads for
*either* the .tar.gz or .tar.bz2 ... and they're almost impossible to
spot in the soup of RPMs and .exes.)

Perhaps we could put the main RPMs (which have higher download counts
-- the FC1 RPM (perhaps artificially) has the highest download count
of any package for beta6) on that page, and stuff the RPMs nobody
cares about somewhere else, with a link.

A yum repository would of course be nice, but many people won't
install a foreign yum repository, but will install individual
packages.

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://pidgin.im/cgi-bin/mailman/private/cabal/attachments/20070325/d3a6c0b3/attachment.pgp