Created attachment 684633 [details] dar-2.6.13.ebuild The latest available version in the portage tree is 2.6.10. I modified the ebuild for version 2.6.13. I tested different USE-flag combinations and added a new flag "librsync" that controls whether dar will be built with net-libs/librsync. That should fix bug #739698. I also tested that new flag. I did not test static builds. Also I added a line to REQUIRED_USE to prevent static building if librsync is enabled. The reason behind this is that the librsync ebuild does not support static builds.
Can you please attach a unified diff file (diff -u old new > patch) showing the changes you did to the ebuild?
Created attachment 684636 [details, diff] patch patch from dar-2.6.10.ebuild to dar-2.6.13.ebuild
We already have a "rsync" USE flag in another package (net-misc/scponly). Would you mind renaming "librsync" USE flag to "rsync" please?
Created attachment 685572 [details] dar-2.6.13-r1.ebuild renamed use-flag "librsync" to "rsync"
Created attachment 685575 [details, diff] patch patch from dar-2.6.10.ebuild to dar-2.6.13-r1.ebuild
Created attachment 685578 [details] dar-2.6.13-r1.ebuild corrected mistake: USE-flags and RDEPEND statements were ordered wrongly.
Created attachment 685581 [details, diff] patch corrected patch against dar-2.6.10 from the tree.
Additionally I'd like to mention that I dropped the ~amd64-linux keyword as there were missing dependencies on that prefix architecture so repoman complained about it.
Sorry, missed this somehow(?) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef2829d1ac400892265dab27dd486e5a8710c740 Looks like we may still need to do the librsync thing though?
(In reply to Sam James from comment #9) > Sorry, missed this somehow(?) > > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=ef2829d1ac400892265dab27dd486e5a8710c740 > > Looks like we may still need to do the librsync thing though? I already implemented it weeks ago, just have a look at the attachment "dar-2.6.13-r1.ebuild" above.
