Chroot build... scripts

[necrose99]

https://github.com/cargo-bins/cargo-binstall

Also github actions... bakes binaries for cargo-bins, ie Arm64 for Macos or embedded etc... riscv64 ie framework 13 laptop shell/riscv64 boards or riscv64 M-ATX boards...
Faster porting of os to other targets

In GitHub Actions

We provide a first-party, minimal action that installs the latest version of Binstall:

• uses: cargo-bins/cargo-binstall@main

For more features, we recommend the excellent taiki-e/install-action, which has dedicated support for selected tools and uses Binstall for everything else.

Docker etc for porting...
docker run --privileged --rm tonistiigi/binfmt --install all
docker pull arm64v8/debian:latest
Apt install -y cargo rust...
Eg cargo binstall moss boulder etc

https://github.com/worproject/rpi5-uefi
Ufei boot stub , grub etc...

Host types debian or Gentoo llvm for porting

Aerynos-stap.sh --buildhost amd64 --target arm64.. ./portarm64-test
Schroot/proot ./portarm64-test

Or /mnt/aerynos-rpi5 , chroot here...
Nvme/sdcard ..

Portage for gentoo is good use flags gives CONTROL and precision...

USE="feature -unwanted" emerge dev-vcs/git

However the rust based build and pm look faster , might be fun to give it a poke...
Especially on embedded platforms...

[bhh32]

Was this written with AI? Please explain what you're requesting or what the issue is in a more coherent way.

[malfisya]

Was this written with AI?

Seems so. This is what OP written in other repo.

[ermo]

Since the OP does not make a coherent suggestion or case for a change, we're closing this as Not Planned.

[necrose99]

1 ] Ok so no ports with moss or bolder for use in building alternatives ie Arm64 or iot like builds..
Of the os ... or ppl porting builds by hand for tinkering...

-- got it..

2 ] Or other ports yet planed, to other architecture..
Ie Arm64, etc...

--'got it no ports planed ?

3] Cargo-binstall , with binaries..
Might have made porting in chroot easier...
As the Cargo-binstall, can automatically build binaries, and for most platforms... or alternatives and publishes them
For alt platform port tinkering: pre-built binaries lower barrier to entry... to build things... or cross build/port items ...
As mentioned they have items to add to repository cargo.toml /github actions
Can bake moss boulder in amd64/arm64/etc...

---was merely a suggestion...

3b] any commodity docker image qemu-static-$target
Mount /osports/$targets/ cargo binstall moss boulder...
Start-building.sh.... @/$targets/

4 ] No debstap equivalent.. or archstrap equivalent.. scripts to setup an equivalent minimal aerynos-chroot... planed either ?
--'aerynos-stap'--- ???

---got it...
Just saying might prove useful in the future...

5 ] Just saying the moss/boulder pm might have some definate speed advantages on even embedded systems... for compiling, upgrading etc.. newest hardware esp.. newest kernels...

6] was curious about posible ports or
Binaries to test build some ports...

Sidebar
[As far as tweaking readme.md Google docs is bit better , for wsywig , seems recent addon..

its a coin toss for gpt..
Ask it to check or improve readme dyslexic mistakes , ie spelling/ grammer gone or
You get it as the Mona Lisa improved layouts in markdown etc..
Md beautification. or a train wreak.. or in-between thier of...
and yes I aim to fix 1st round draft ..
I mays well do it old school in html formatting won't go tits up .... at times... md can be infuriating... or never cooperates...

[ last item daydreaming for a caffine break , hammering resumes out ... via usual platforms... till ones eyes bleed , juggling interviews etc.. i haven't had a chance to poke at 1st round draft n fix it used a gpt shell to collate etc items to add draft]

[ermo]

Your original post was so rambling and difficult to understand that we closed it, because it was not clear what you were asking for or what you were hoping to be able to achieve.

A bit of unsolicited advice: The clearer and focused your writing, your problem statement, and your question all are, the more likely you are to get a useful answer.

In the future, you might have more success engaging in our github discussions instead.