Arch Linux User Repository

Lorde, thanks for clarification. I will think what can be done to automate this steps, keeping package simple.

Sorry, I didn't provide the clarification you requested. The btsync@.service in bittorrent-sync runs btsync-wrapper, which checks if ~/.config/btsync/btsync.conf exists, creates it (using btsync-makeconfig) if necessary, and then runs btsync. The btsync.service does not use btsync-wrapper since a default config file for that service is included in the package. btsync-makeconfig is just an option-driven frontend to `btsync --dump-sample-config | sed 's/foo/bar/' | sed 's/boo/far' | ...`

ava1ar: The use case I imagined is that the user that installs the package may not be the only one that will use it. alice installs it and follows the post-install instructions, runs systemctl start btsync@alice and everything is well and good. But when bob notices that btsync is available on the system and does systemctl start btsync@bob, it fails silently. Of course, he could just look in journalctl and see that the config file could not be read, google how to create one and do so. I agree that we do not *need* the script, but I can imagine that more than just a few people would find it handy, and thus there is reason for it to exist in AUR. But, like I said, it would probably be better off in an optional add-on package. I'll see if I can pull that off using only clever systemd definitions, and no modifications to this package. If so, then I'll probably refactor the bittorrent-sync package to only provide the config creator script, and delegate the core functionality to this package.

Lorde, Thanks for pointing out LICENSE.TXT file - I updated package to use it, instead of file copies. What about additional scripts for creation ~/.config/btsync/btsync.conf, can you please clarify, what exactly they are creating there and why can't this be done manually once, rigth after first install? I have all required steps listed in .install file, you need just copy and run command from there and then adjust file content as per settings you need - is it so difficult? I can even add sample setting to this install file, but I still disagree, that we need separate script to do this one-time action.

On both my machines btsync started with systemd does not work properly - for some reason the service starts properly , but just does not connect with other machines (I suppose it needs other survices (for ex. networking) started at nearly the same time ) . When I reastart it with systemctl everything is ok . My desktop is GNOME . Workaround : start the application with startup programs through the gnome-session-properties configuration tool with the line /usr/bin/btsync --config... etc. from the systemd service (for reference see systemctl status btsync@.. ) . Edit : that doesn't solve it either ... (at least not every boot) . Any ideas on troubleshooting the problem ?

Oh, and one more thing: my opinion is that the LICENSE.TXT distributed with the executable should be included in the package. Perhaps the privacy policy too, but both it and the terms of use are referenced in LICENSE.TXT.

ava1ar: The garbage is, functionally, exactly one thing: auto-creation of a ~/.config/btsync/btsync.conf if it doesn't exist. That said, you have a very valid point, this is much more in line with the Arch Way. Part of me now wants to drop bittorrent-sync, but it'd be a shame to let the work put into the garbage go to waste (no pun intended :P). Perhaps we could devise a way for the garbage to be available as an add-on for those who want it, and let this KISS package be the default?

Could I suggest adding at least Nice=19 in the systemd service units... This is supported under both the standard CFS and the alternative BFS kernels... The service is, in my experience, a real CPU hog!!

ottomodinos, good catch. Let me check this and come back with the answer.