Community Packages

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!
Tasklist

FS#28384 - [quassel] split package: core and client

Attached to Project: Community Packages
Opened by sorcix (sorcix) - Sunday, 12 February 2012, 18:26 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 27 May 2013, 09:11 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Vesa Kaihlavirta (vegai)
Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When installing quassel on a server where only the core will be used, loads of client dependencies are installed as well. Please split this package in a "core" and "client" package, so that the core can be installed separately.
This task depends upon

Closed by  Jelle van der Waa (jelly)
Monday, 27 May 2013, 09:11 GMT
Reason for closing:  Implemented
Additional comments about closing:  they are now quassel-core and quassel-client
Comment by KaiSforza (KaiSforza) - Monday, 12 November 2012, 23:36 GMT
Quassel has packages in the AUR for just this occasion. (git versions of both as well.)
Core: https://aur.archlinux.org/packages.php?ID=42084
Client: https://aur.archlinux.org/packages.php?ID=42085
Comment by Greg (dolby) - Monday, 19 November 2012, 06:51 GMT
Decision?
Comment by Jelle van der Waa (jelly) - Monday, 27 May 2013, 09:10 GMT
I've implemented the split packages, they are now quassel-core and quassel-client

Loading...