yes i'm aware of bug #233808, but starting with the 0.3.1 release the monolithic build was improved to allow users not interested in the distributed feature to run it easily in "standalone mode". In monolithic mode, quassel runs with a single process (using an internal connection to the core, the binary is called simply "quassel"), i was able to build and use it. (Changelog:) "[..] * Monolithic build features zero configuration: Click'n'Run * Monolithic build now uses a proper (socket-less) internal connection [..]"
Hm, given who is maintaining quassel now, I think you may have some luck getting your request ;) Assigning to maintainers.
(In reply to comment #1) > Hm, given who is maintaining quassel now, I think you may have some luck > getting your request ;) Chances are high indeed. ;-) I am aware of the improved monolithic build but I did not have time to implement it yet. I am away until January the 6. but when I am back I will take a look at it.
(In reply to comment #2) > (In reply to comment #1) [..] well, nice! thanks a lot for your feedback i will wait for the official ebuild :)
Patches from Daniel committed, thanks and keep up the good work
