Created attachment 899033 [details] spec diff Description of problem: Hexchat automatically loads all plugins in plugins directory, and some people probably don't want that (I'm one of them, and I hope not the only one). Currently it is not possible to disable it (maybe I'm wrong, but I tried to look for a solution), so I wanted to request this "feature" to split hexchat to hexchat-plugins which will have additional hexchat plugins like (checksum, doat, fishlim, sysinfo), I created edited current spec file, I'll attach the diff. In my "solution" I left python and perl plugins which are needed for scripting (I think that is good feature to have in base package?). rpmlint complains on -plugins package about spelling errors in plugins descriptions (plugin names), not sure is there a way to avoid this, because they are not spelling errors. $ rpmlint ../RPMS/x86_64/hexchat-plugins-2.9.6.1-1.fc20.x86_64.rpm hexchat-plugins.x86_64: E: devel-dependency pciutils-devel hexchat-plugins.x86_64: W: spelling-error %description -l en_US checksum -> check sum, check-sum, checks um hexchat-plugins.x86_64: W: spelling-error %description -l en_US doat -> toad, dost, dot hexchat-plugins.x86_64: W: spelling-error %description -l en_US fishlim -> fishily hexchat-plugins.x86_64: W: spelling-error %description -l en_US sysinfo -> misinform Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Sorry, I forgot to ask if hexchat-plugin from my current spec/diff will depend on hexchat package, or it needs some extra requires lines?
Created attachment 899035 [details] diff_01 Changed "Requires" to "BuildRequires" to fix rpmlint error "hexchat-plugins.x86_64: E: devel-dependency pciutils-devel" Thanks to 'misc' from #fedora-devel
Another problem I see, now in base package /usr/share/doc/hexchat contains 'fishlim.md', it probably needs to move to hexchat-plugins package. I thought it would be easy, but what I did is a mess, nothing useful!
I understand some people may not like 'clutter' but what real value does moving these provide? The optional plugins are extremely small, use relatively no memory, and are mostly only triggered on specific commands (e.g. /sysinfo) that you can ignore?
It is really hard for me to give good arguments against shipping plugins with base package. First they are plugins, and should be optional, second they are not very useful plugins that we need to include in default package, and probably most people don't use them. No better arguments from me, if I remember something I can comment here again, but you are free to do what you want. ;-) Or maybe upstream should change the way how they handle plugins, and allow users to load plugins manually and/or disable autoloading (make autoloading optional)? I thought this is the way to make it optional in the distribution, and I think it is not hard to maintain?
>and probably most people don't use them. Based on the amount of spam I've seen of /sysinfo on irc I think its used. :P > Or maybe upstream should change the way how they handle plugins, and allow users to load plugins manually and/or disable autoloading Yes that would be the best solution. >I think it is not hard to maintain? It wouldn't be hard to maintain. The issue I have with it is fedora has no system of 'recommends' for packages. So 100% of users will just never know hexchat-plugins exist and while they may not be super useful a few will come in #hexchat asking how to get /sysinfo. OpenSUSE did this the opposite way you suggested; They threw the tiny plugins in the main package and moved the bigger ones (Python, Perl) into their own package since those actually pull in deps. I think this is the worst solution for users. All other distros just have one package afaict. So personally I see no harm in keeping them all in one package. It adds waste for a few that care and extra features for a few that care.