create repo ... with a side order of snafu....

[necrose99]

define arches...... ??? so noper and double nope nope...

REPOSITORY_NAME=Maverick REPOSITORY_DESCRIPTION="Unofficial Arm64 Community repo +AMD64 Crosscompile toys and QEMU for amd64/arm64 chroots " sabayon-createrepo

---

root #echo 'QEMU_SOFTMMU_TARGETS="alpha aarch64 arm i386 mips mips64 mips64el mipsel ppc ppc64 s390x sh4 sh4eb sparc sparc64 x86_64"' >> /etc/portage/make.conf
root #echo 'QEMU_USER_TARGETS="alpha aarch64 arm armeb i386 mips mipsel ppc ppc64 ppc64abi32 s390x sh4 sh4eb sparc sparc32plus sparc64"' >> /etc/portage/make.conf
#gentoo embeded wiki....

---

portage packages amd64 nice to haves crossdev usual's ok no problemo...

hacking-gentoo ... > quemu wrappers... and other chroot aarch64/arm64 qemu or statics... for chroot's
mainline sabayon qemu dosent support arm64 (/grumbles) but with local server can fix this..
binutils with +multitarget , makes crossing more easier just takes dammed longer to build...

https://www.dropbox.com/sh/4u9gbhps0ek402e/AAC5VLBE32cwH2gGjkj0Yz9sa?dl=0 custom packages
including equo , rigo etc ... and other sabayon/sabayon-distro keywords="~amd64 ~x86 ~arm & <<< ~arm64"

https://isshoni.org/pi64/ mainline gentoo packages for pi3 in 64 bit..... upstream binhost...

https://isshoni.org/pi64/Packages

(I've hacked ABI support for ARM=32 64 /Mutilib ... , added 32 bit back to the kernel ... point being is the existing packages on sabayon ARM... and eases migration...
other main point was to see if setting up an full arm64 server with docker etc viable... or no...)
and for a dash of #pentoo could get and load pi's for Redteam runs much more quickly.
equo.sql mod for arm64 , symlink aarch64 @ arm64 just incase...

https://isshoni.org/pi64/Packages

ACCEPT_KEYWORDS: arm64 ~arm64
ACCEPT_LICENSE: @free CC-Sampling-Plus-1.0
ACCEPT_PROPERTIES: *
ACCEPT_RESTRICT: *
CBUILD: aarch64-unknown-linux-gnu
CHOST: aarch64-unknown-linux-gnu

---

start the build , lets inject some packages with the docker thing'y....

lets add arm64 packages also , hmm what could possibly go wrong hear ?           adding them to AMD64
double facepalm , double face deskk... oh no'ze ......
I figured it might pick up and add to aarch64 or arm64 but nope lets add this little ....

define arches , amd64 , ARM64 ARM64-rpi or ARM64-iot.. this for the moment I cant seem to do. ARM64 packages path... =

not only dose the metadata fail to get the cputype , say oh custom new arch... just faster to sshfs & pull bins than on RPI3 i 64 bit ... equo smart inflate... for added amusement it then adds to amd64 entropy repo ... i even created the arm64 /aarch64 folders... , had this been put on the interwebs in production it would have been far less amusing as equo will get the package and kerblewy their went python-3.4.x
equo/portage etc are dead.... or worse...

equo smart inflate i dont have a manual eit script for now....
@wiki community repo mavrick the unofficial arm64 repo of stuff. ....
slowly build up a repo for "gits and siggles " ...  then rsync to a host...

[necrose99]

equo.zip arm64 db...
generate-equo-arm64.zip

caveats INSERT INTO "settings" VALUES('arch', 'ARM64'); could use an alias aarch64=ARM64

however with equo *.7 ... is recent not yet not rebuilt to newer yet. the sql on the rpi3 least lets most of the entropy eit run etc albiet slower than a pentium III when under load over ssh...
equo up takes the usual time..
though you can build docker , etc just 4-8 gigs would be posh for sabayon devkit...... or a few banani-pi's in cluster.. they can equo smart inflate etc... on small packages , however gcc kernels .....ugh.... were's ansilble /puppet matter plugins... for jenkins... so you can bot that shit'e...

Python-3.5 tends to FRY and brake crap and corrupt .. python-3.6 is nicer and less corupt'y under arm64 ... might be good to kill 3.4/3.5 in time ... so far so good..
also seems more stable under normal AMD64 desktop use on my main install ...
pi3 systemd swap was a misseralbe fail , so I have to recover... use my backup image , debian working on card has more ish.. if i move it to BPI64 could be usefull as distcc slaver...
need to recover my Gentoo card n scape it tar it.. rebuild it..
sabayon zenmap works nicely.. as namp is on the image , xforwad and wala or MobaXterm...
and you can use zenmap fe , a script to scape keywords from ebuilds or append ~arm64 ...
as hand hacking is a bitch... or shoving by path emerge %path%/ebuild-9999 ...
takes some doing for pentoo items fustrating ... however as a Pen-box.. could be fun...