Thanks again to @SweetAIBelle for extensive contributions to OS/1337, making the pipeline and scripts to reproduceably build OS/1337 images and it's parts more flexible and nifty.
And this one of these things that's both for me and everyone else. Having profiles means you can do experiments in separate profiles & easily have bigger profiles for when you don't need to fit on a floppy.
I do still have other things that I'll eventually rework. Downloading & unpacking should really be done in each packages script, & some of the numbered scripts will probably end up in the pkgs folder. I want to make it a little easier to run stages of the build separately.
I also want to add a bunch of packages into the pkgs folder, but there's still something up when running them... (Both kilo & dbclient error out when run. The latter isn't specific to my scripts...)
I will say keeping track of what folder the script is running from is rather a pain in the scripts...
@SweetAIBelle I think this is great forward-thinking on your side since OS/1337 should long-term be developed into a robust yet "clean slate" for #minimalist#Linux that isn't as bloated as #Yocto but remains customizeable and flexible.
@SweetAIBelle After all, I think that longterm OS/1337 should provide a simple yet versatile basis to expand to arbitrary complexity if desired, offering more features than @landley 's #mkroot since I'm convinced that a package manager [ https://github.com/OS-1337/spm ] and accompaining repository [ https://github.com/OS-1337/pkgs ] is obviously out-of-scope for the backbone of #Android, where everything interactive is ment to be on the fancy GUI layer for good reasons...
@kkarhan@landley@OS1337
And I don't really mind reinventing the wheel if I'm having fun doing it. It keeps me in practice and is a fun project even if it's doubtlessly been done many times before.
@kkarhan@OS1337@SweetAIBelle It's package management that's the real can of worms exerting black hole gravity on a dev team. That's why I'm looking to leverage an existing package management system, currently eyeing devuan.
Toybox currently has the problem that I have enough users I'm getting a constant stream of interrupts via bug report or feature request. "Such problems we should have", but the swap thrashing has slowed the march to 1.0 significantly.
@kkarhan@OS1337@SweetAIBelle Just my tool chain build script is still leveraging musle cross make, which is using old package versions for everything and has dozens of patches it applies to them.
@kkarhan@OS1337
Thanks. It's one of these areas where I think different people will want different things from a minimal os, and this adds more flexibility to the project to accommodate them.
I do feel like there's more to in on the dbclient front. If you look at this screenshot, you can see both it and kilo erroring in the same way, and I don't think kilo does anything internet related...
@SweetAIBelle As of now I've not gone deep into either, but please open up an issue re: #dbclient so I'll come back at it once the network stack is iron'd out...
@kkarhan
Alright. I was planning on adding a few more programs at some point to see how general the issue is.
I don't necessarily need kilo to work, but given that it's a functional text editor in 32k, it seemed rather smaller than some of the other alternatives. (It's also roughly 1k lines of code with no dependencies...)
My main concern here was that it's the same error message at the same spot with the same code as dbclient.
Add comment