Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39756 - [quassel-client] Flawed packaging
Attached to Project:
Community Packages
Opened by Fredrik Haikarainen (Haikarainen) - Saturday, 05 April 2014, 14:00 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Wednesday, 08 October 2014, 14:20 GMT
Opened by Fredrik Haikarainen (Haikarainen) - Saturday, 05 April 2014, 14:00 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Wednesday, 08 October 2014, 14:20 GMT
|
DetailsDescription: Since Quassel can come in 2 variations, monolithic or split up into a client and a core, so by standard logic it should have 3 packages; quassel-monolithic (or likewise), quassel-core and quassel-client. Currently the packages available are quassel-core and quassel-client, the latter provides both the monolithic client and the stand-alone client, which I feel do not comply with Arch's philosophy of minimalism/being lightweight and the "you only get what you ask for" mentality of the userbase. It's also worth to mention that this method of packaging is confusing with the quassel-client's description is as follows: "Qt4 IRC client with a separated core - client only", which implies the monolithic client would not be provided here.
I feel that a packaging method for quassel should have these 3 options (as stated above): 1. The core, as it is now in quassel-core 2. The stand-alone client, in quassel-client 3. The monolithic client (no need for separate core), in quassel-monolithic (or likewise) This would completely remove all of the current confusion, and make the options you get more reasonable and slipstreamed towards ArchLinux's philosophy. Another option would be to at least fix the description of the quassel-client package, although I personally feel the other solution would be better. |
This task depends upon
Closed by Jaroslav Lichtblau (Dragonlord)
Wednesday, 08 October 2014, 14:20 GMT
Reason for closing: Implemented
Additional comments about closing: monolithic part is now split into quassel-monolithic package
Wednesday, 08 October 2014, 14:20 GMT
Reason for closing: Implemented
Additional comments about closing: monolithic part is now split into quassel-monolithic package
At least fix the description if you're too lazy to do it properly, because right now the quassel-client description states that it only includes a standalone client, and it is extremely confusing (especially since the wiki had no information on quassel before I filed this report and started one).
EDIT: Sorry, I thought Doug was the one assigned.