Is it possible to add the monolitic client? It is a bit annoying when one always needs to start core and client separately, especially when you don't need them separated! A quick workaround for the ebuild would be removing $(cmake-utils_use_want X QTCLIENT) -DWANT_MONO=OFF and replacing it by $(cmake-utils_use_want X MONO) in src_compile.
No the monolithic client is not build by decision. Please contact upstream, I think there were plans to remove that entirely.
(In reply to comment #1) > No the monolithic client is not build by decision. Please contact upstream, I > think there were plans to remove that entirely. Okay, I somehow thought you did this on purpose :-) I was told upstream at #quassel how to build the monolitic client and nobody mentioned a possible removal of this functionality. So it would be probably better to use an init script for a convenient handling of the core, like you mentioned in bug 217510. Although I find it rather strange to use an init script, because I for myself don't want the script in a runlevel because will probably only start the core when using quassel. So it would be nice to have this automated. Is it somehow possible to use a script which starts the core in the background when the client is started from the menu by using the desktop file. If yes it would be nice to add this to the ebuild as a second option besides the init script to start quassel. Regards, Daniel
To be entirely honest, I don't see what is the point of using quassel in that way beside development, really, so I'm sorry but I'd rather not add any more USE flags to handle the monolithic client. As for other feature request, please direct them upstream.
(In reply to comment #3) > To be entirely honest, I don't see what is the point of using quassel in that > way beside development, really, so I'm sorry but I'd rather not add any more > USE flags to handle the monolithic client. As for other feature request, please > direct them upstream. No problem I think I can get used to an init-script. Also lately my irc client runs permanently anyway, so it would be no problem to have the init script in default runlevel. Do you mind sharing the init script you use for yourself. Or will you add it in the near future? Regards, Daniel
(In reply to comment #1) > No the monolithic client is not build by decision. Please contact upstream, I > think there were plans to remove that entirely. > from #quassel [19:30:00] <billie> btw. flameeyes told me the the monolitic client will be removed in the near future is this true? [19:31:25] <Sput> billie: no, it will be made useful at some point, by actually providing a simplification for users not needing distributed quassel [19:32:10] <Sput> billie: it's no longer built by default, since it currently just confuses users So why not building the monolithic client and give some info how to use monolithic and distributed versions in an elog message?
Made useful _at some point_ though. Right now it really is not, as Sput says it's just confusing. No I don't feel like this is going to happen for 0.2 series, I reserve a later evaluation, but not for now.
