I'm think boxbackup.ebuild need split on two part: server-part & client-part. Why? This is backup app. Client-part install & running offten, server-part rarely. Why i'm need install server-part on clients ? PS I'm added split ebuild to bug #82447, but when bug closed... i'm got in portage three not splitted boxbackup-0.09.ebuild. PPS Sorry my english very ugly ;) Reproducible: Always Steps to Reproduce:
I'm hestitant to split the ebuild, since upstream doesn't split as well as accomodate in any way to have a split setup, IMHO. I see your point, but considering the other packages in app-backup it doesn't look to uncommon to me not to split. The only think I could think of is having a "client-only" USE flag as in bacula, but then some obvious way to only install the client should be in the build system. Simply 'rm -f'-ing might be enough as well. Opinions?
Okey. USE flag "client-only" also good solution.
Sorry for the delay. I committed boxbackup-0.09-r1 which has a client-only USE-flag. reopen this bug or open a new one if any problems occur.
I'm reopen bug. Where is init script for boxbackup client ? It's may running in daemon mode.
there should be a bbackupd script for the client. I don't understand the problem.
> I don't understand the problem. boxbackup-client can operate in daemon mode, for this need init script.
(In reply to comment #6) > boxbackup-client can operate in daemon mode, for this need init script. This script is called bbackupd and is located in /etc/init.d/bbackupd The ebuild is creating this one unconditionally, so it should always be there...
Huh. It's my mistake. Sorry
