as for uri i can work the ebuild to add arm6/arm7 safely however arm64 works. just not as of aware on EABI that are valid for gentoo ie arm7-hardfload. vs arm6 .. repoman is griping as i included them just incase. arm64 will ebuild {package,merge,clean} on bump w/o question , wich is useful for rpi4-herd to a server for binhosting 3 or 4 x rpi4's > server as i build insted of having to run rsync or etc etc.. Reproducible: Always arm? ( ${BASE_URI/@arch@/armhf} ) any tips to resolve armf vs armel would be useful as i can clean up this pull. " # https://download-cdn.resilio.com/2.7.1.1370/Debian/resilio-sync_2.7.1.1370-1_arm64.deb # https://download-cdn.resilio.com/2.7.1.1370/Debian/resilio-sync_2.7.1.1370-1_armel.deb # https://download-cdn.resilio.com/2.7.1.1370/Debian/resilio-sync_2.7.1.1370-1_armhf.deb
Off the top of my head, I'm not sure how we're supposed to figure out which binary to use for arm (hardfloat or not). I'll have a think and look for examples too. Thanks for the info!
armel for arm6 arm7hf for arm7 just trying to server correct bin to arm6/7 platforms. arm64 already built package locally , and no qualms anycase i can hopefully tidey p my pull request with more appropriate url and more properly finished ebuild.
