make an auto-fork of a repo , IE emerge-sync gentoo ,and or /layman-ic overlay ie pentoo make a fork via rsync on done. ie gentoo-arm64 in /usr/local/overlay/gentoo-arm64 $reponame-$arch.. drop packages already maching $arch ie arm or arm64 or specified. into keywords: KEYWORDS="~amd64 ~arm ~ia64 ~mips ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos" change or append $Arch via sed or script if keywords not present then not an issue , can also drop.. & repoman manifests in dynamic-clone repo KEYWORDS="~amd64 ~arm ~arm64 ~ia64 ~mips ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos" build packages... option to offer diffs, logs etc via email to gentoo team arch-name some team.... -build-Success @gentoo.org (long term packages can have keywords appended at leisure) sort term would shut up the nagging on emerge and me having to bug report it .. EVERY TIME , prertyy please package builds update key words ..... X 100, 1000 packages... heck might even have email > script auto fix keywords on successes .... offer-epic-fails @ arch-tem-name-build-fails@ gentoo.org ... build logs... etc.. patches can get made, etc , would be a nice to have along with CROSSDEV squashfs for embed fork testing also a nice to have. esp to save room on some embeded things ie RPI3... Reproducible: Didn't try
KEYWORDS= not in ebuild/s dont need to have a copy.. keywords has arch ie arm64 , can drop... for ebuilds missing the chosen $arch in the keywords append it in... */*:gentoo ~arm64 , /etc/portage/ package-accept-keywords etc.. fails often.. package.use ~$arch in this case fails.. also easy to fat finger. p7zip lzma etc hot edit , fix with repoman by adding in ~arm64 in my use case fixes it. however with a OMG number of packages , doing this by hand could get ugly.. also next emerge --sync will kill any hotfixes.. less added to a local overlay which could grow quickly stale.. emerge -sync main tree, clone , packages missing ~$ARCH in keywords , (KEEP) AUTO HOT Patch Keywords in Ebuild/s "Auto-magically" in clone/s repo/s repoman auto-clone/s repo after... for manifests... on the back end. New CPU $ arch comes out , less hell to test... in the future... automate new $Arch testing in docker... perhaps... ? Automate keyword fixing and package builds on new $Arches faster.. Perfect add on with crossdev.. catalyst etc. option to automate sending feedback logs.. feed back fixes that work.. auto-github , etc, email etc.. diffs logs etc. feedback build fails for new patches.. nutshell: would be a nice to have , for users/devs a like. as more RPI like options get dirt cheap , having a firewall Gentoo etc on a mini-brick or arm64 (or newer cpu arches not yet contemplated).. ie blade servers , could yield to much faster testing , and or more immediate use.. faster turnaround.
Michael, I tried to understand this report and discussed it with other developers. But we do not understand your recent reports. Please read a few other reports and the wiki [1] to get an impression how to improve. We agreed, that we have to close this ticket, because we can not understand it. I hope you can understand this. [1] https://wiki.gentoo.org/wiki/Bugzilla/Bug_report_guide
1:) fork a repo for testing... (having a post-hook auto-fork toy...) (having a set of scripts to do this on emerge --sync ...) 2) fix the keywords for testing.. (and or user/s less annoyed and having to hand hack every flipping ebuild... for say ~arm64 or CPU of choice...) 3) repoman will fix the manifests. in background. 4) cross compile or native compile. 5) at user option mail logs back to gentoo , build ok , item can get marked for keywords as ~ or $ARCH... and or fixed for $arch, (ie arm64) ie Gentoo-local ... /usr/portage/ > clone to /usr/gentoo-local GREP/sed ?? **post-hook perhaps** to rsync a repo to /usr/local/X? anyhow most ebuilds are stable for X86 or AMD64... however I've also been building for ~ARM64 A: test an ebuild... cd /usr/.... nano ebuild.... Keywords..... < ~arm64 .... UGHH how annoying... after the 200th... ebuild... or cd /usr/portage/??/?? emerge *.ebuild so making an auto-fork of Gentoo and or laymanic repo's Auto patching Keywords=Myarch ~myarch IE arch your testing... arm64 in my case.. SEND FAIL / SEND Success logs to ???? @ gentoo.org. emerge --sync , main repo done post hook rsync a copy to /usr/local/gentoo-$arch find ebuilds fix keywords... for $arch.... background repoman and fix my clone.. volunteers could test packages with more automation... as well some packages have few deps ... but those deps have a crapton of hidden deps. my main point is if your not wanting to keyword a lot of ebuilds by hand making a fork and not having to do this every emerge -sync or layman -S and having this find ebuilds this could help do keyword testing far more quickly. https://github.com/sakaki-/gentoo-on-rpi3-64bit https://www.dropbox.com/home/sakaki--gentoo-on-rpi3-64bit granted i need to migrate to a softIron arm64 server.. as the PI3 has just a touch less ram at times.
I understand that you want to suggest a new feature, but I do not understand what it should be good for or how it exactly works. As we can not really discuss on a bug tracker, I close the ticket here and suggest you discuss the idea in a forum or on IRC.
