fredx181 wrote: Thu Aug 08, 2024 4:59 pmwiak wrote: Thu Aug 08, 2024 2:42 amwanderer wrote: Wed Aug 07, 2024 8:43 pmthe solution to fredx181 dimkrs wiaks and rockedges concerns about the downsides of modularity
can be solved by having the package manager download the app
and then package it into an sfs file with a script
so that everything is automatically compatibleYes that does work ....
...Ok, it can work but is there a real advantage compared to a 'single' SFS module ?
I think it's only useful that way for very advanced users, not for the average user or beginners.
So, in other words, not user friendly at all IMO, unless there's a easy way included in the system to accomplish that . Big challenge to make that foul proof (not saying it's impossible though).
Well, as we all know, and I'm sure wanderer would agree, he is a real fan of tinycore linux and what he describes is always close to that distro build model. Now, I used to use tinycore a lot, back in the days I was also using old Puppy Linux 2.17. So I spent hours and hours configuring tinycore linux with all these tcz (sfs) addons, to get as close as I could to the operating system I wanted. Each time I gave up - the effort was ridiculous compared to simply booting up old Puppy Linux. Years later tinycore linux still fascinated my, so flexible and fun to assemble, but the pain... I agree that next to no-one who simply wants a flexible but easy to use distro would EVER use that multi-tiny sfs app approach (be they layered in or symlinked in) - it is just too much work. Great hobby though.