Re: aMSN plugins

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sander Hoentjen wrote:
Hi,

I am currently the packager of aMSN (and I intend to stay that). aMSN is
an msn clone in a sense that it tries to mimic the looks and
functionality of the official client, and more. For the more bit aMSN is
extensible with various plugins. The upstream release tarball always has
a few plugins included, so i made amsn and amsn-plugins from that
source. There is also module in cvs with extra skins and plugins, and
there exist various plugins and skins contributed by users. Should i
create 2 extra packages, one for skins, and one for plugins, or a
package for each skin/plugin?
Also if one package for all plugins should be created how should i call
it, something like amsn-plugins-extra or should i remove the
amsn-plugins from the amsn.spec and include those plugins in
amsn-plugins.spec
something like amsn-plugins-extras is better (they wont need that much disk space so splitting it wont make sense)
Any hints would be appreciated

Sander



--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list

[Index of Archives]     [Fedora General Discussion]     [Fedora Art]     [Fedora Docs]     [Fedora Package Review]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite Backpacking]     [KDE Users]

  Powered by Linux