You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
set this as more **Backend infra bits ** or experimental bits. and or experimental images options / git pulls as needed.
Rpi4 booting with Grub and the firmware is on list to do..
can pin Variant images and or experimental builders hear , once stabilized can be pushed into the more production ready org https://github.com/GenPi64
@perkinslr has a BTTRFS build ability to roll items back etc. however docker is basically ephemeral
when the run dies other than mounts the shell dies poof , so for those of us on ext3 etc but not BTRFS/ZFS desktops vs servers this should run well @ home. on home desktops , ie ryzen 7 i7-gen7-9 i9 etc.
then docker offers similar build options of repeatable...
Gentoo recently has an arm64 autobuilder on docker hub built on Travis and pushed. , thus making a Genpi64 builder Docker quite simple to do.
or a Rock64 /etc package builder to push to a coretex-arm64 repo should be quite simple..
rock64 has but a few firmware loaders etc.
and or on a native hosts have a clean chroot for builds via docker every single time.
however Profile bits may be added to mask rock64 packages and settings from rpi4/3 etc.
Likewise mask rpi4 specific packages away from variant boards. however re-use 95%++ of same packages..
rpmdevelop , and scripts , I could extend the defconf kernel to a more universal kerenal arm64 options since >=5.6 most of the rpi/rock64/etc aarch64 kernel has made it to gentoo/pentoo or similar kernels..
hopefully a device set-me-up.sh to append config.txt
rpm build is doable , then inherit rpm or via rpm2tgz make a ready to go set of tarballs.
The text was updated successfully, but these errors were encountered:
https://github.com/GenPi64
add proper links
set this as more **Backend infra bits ** or
experimental bits. and or experimental images options / git pulls as needed.
Rpi4 booting with Grub and the firmware is on list to do..
https://github.com/arm64-gentoo-images/ move personal code repos hear however primary is GENPI64
can pin Variant images and or experimental builders hear , once stabilized can be pushed into the more production ready org
https://github.com/GenPi64
@perkinslr has a BTTRFS build ability to roll items back etc. however docker is basically ephemeral
when the run dies other than mounts the shell dies poof , so for those of us on ext3 etc but not BTRFS/ZFS desktops vs servers this should run well @ home. on home desktops , ie ryzen 7 i7-gen7-9 i9 etc.
then docker offers similar build options of repeatable...
Gentoo recently has an arm64 autobuilder on docker hub built on Travis and pushed. , thus making a Genpi64 builder Docker quite simple to do.
or a Rock64 /etc package builder to push to a coretex-arm64 repo should be quite simple..
rock64 has but a few firmware loaders etc.
and or on a native hosts have a clean chroot for builds via docker every single time.
however Profile bits may be added to mask rock64 packages and settings from rpi4/3 etc.
Likewise mask rpi4 specific packages away from variant boards. however re-use 95%++ of same packages..
rpmdevelop , and scripts , I could extend the defconf kernel to a more universal kerenal arm64 options since >=5.6 most of the rpi/rock64/etc aarch64 kernel has made it to gentoo/pentoo or similar kernels..
hopefully a device set-me-up.sh to append config.txt
rpm build is doable , then inherit rpm or via rpm2tgz make a ready to go set of tarballs.
The text was updated successfully, but these errors were encountered: