Hi, when you install app-backup/spideroak-bin with "headless" USE flag the ebuild will set the line exec "/opt/SpiderOak/lib/SpiderOak" --headless "$@" in "/usr/bin/SpiderOak". So every time you call SpiderOak, you will also set "--headless" parameter. This will block the required [1] "--setup=-" call required for new installations/on first usage. Suggestion: Replace the "headless" USE flag with a "X" USE flag and don't hardcode a parameter like "--headless". So people who don't want the UI will set "-X" USE flag (like they do on other applications) and everything works. Remember, "--headless" is one option... but "--batchmode" is another one people using SpiderOak on server maybe want to use (but a hardcoded "--headless" will prevent this, too). So hardcoding "--headless" parameter is never a good idea. [1] https://spideroak.com/faq/questions/1017/how_do_i_set_up_a_new_user_from_the_commandline Reproducible: Always
(In reply to Thomas D. from comment #0) > Hi, > > when you install app-backup/spideroak-bin with "headless" USE flag the > ebuild will set the line > > exec "/opt/SpiderOak/lib/SpiderOak" --headless "$@" > > in "/usr/bin/SpiderOak". > > So every time you call SpiderOak, you will also set "--headless" parameter. > This will block the required [1] "--setup=-" call required for new > installations/on first usage. > > > Suggestion: Replace the "headless" USE flag with a "X" USE flag and don't > hardcode a parameter like "--headless". So people who don't want the UI will > set "-X" USE flag (like they do on other applications) and everything works. > Remember, "--headless" is one option... but "--batchmode" is another one > people using SpiderOak on server maybe want to use (but a hardcoded > "--headless" will prevent this, too). So hardcoding "--headless" parameter > is never a good idea. > > > [1] > https://spideroak.com/faq/questions/1017/ > how_do_i_set_up_a_new_user_from_the_commandline > > > Reproducible: Always @Thomas, care to provide a patch so its clear what you are suggesting? @Dennis, is this change okay?
ping
I am fine with changing the condition from +headless to -X. I do not care much about using SpiderOak in at -X environment, so please remove the automatic --headless, if that improves the experience for the +X users (which will probably be the majority). I currently cannot test any of this, since I am still a few weeks away from having access to my Gentoo (+X) machine.
I just removed headless. I don't use it. And if you don't, then really there's no one testing. We can always re-add it if there is a request.
I have to re-open the issue: The current fix solves problem, but will pull in [...] x11-libs/libICE x11-libs/libXau x11-libs/libXdmcp x11-libs/libSM x11-libs/libxcb x11-libs/libX11 x11-libs/libXt x11-libs/libXext x11-libs/libXrender x11-libs/libXmu [...] which I don't need on a server/headless system. Please consider adding the "X" use flag like I suggested in comment #0. For me it is the same like app-misc/mc... mc also has the "X" USE flag.
(In reply to Thomas D. from comment #5) > I have to re-open the issue: > > The current fix solves problem, but will pull in > > [...] > x11-libs/libICE > x11-libs/libXau > x11-libs/libXdmcp > x11-libs/libSM > x11-libs/libxcb > x11-libs/libX11 > x11-libs/libXt > x11-libs/libXext > x11-libs/libXrender > x11-libs/libXmu > [...] > > which I don't need on a server/headless system. > > Please consider adding the "X" use flag like I suggested in comment #0. > For me it is the same like app-misc/mc... mc also has the "X" USE flag. Sorry, I interpreted your request as not caring for headless or -X, and only caring for the gui. (If you want to get a developer to do it right the first time, send a patch!) Please test spideroak-bin-5.1.8-r2.ebuild and see if its what you want. Reopen if there are still any more issues.
Thx! -r2 does exactly what I was looking for.
