I was reading a thread the other day concerning MiSter. Evidently, the buildroot hasn't been relinquished to the public. But, shouldn't that be dispersed openly, too? The cores have to be, of course. But why not the buildroot? Forgive my ignorance, just trying to understand.
-
-
Replying to @Voultar
CentOS was a project that recreated the entire RedHat Ent Linux buildroot since RHEL didn’t give it away. The linux distro in the MiSTer is tiny by comparison, and we can already compile binaries for it. Its not a very high hurdle. Won’t get far with a fork if this is the blocker
3 replies 0 retweets 0 likes -
Replying to @Bender65816 @Voultar
It seems inevitable that MiSTer will be forked (like MAME was) and that might lead to cool things or could dilute MiSTer, or confuse people, who knows? The lack of buildroot isn’t a real obstacle, though.
1 reply 0 retweets 0 likes -
Replying to @Bender65816 @Voultar
"The lack of buildroot isn’t a real obstacle, though" it is a pretty damn big hurdle. Let's not minimize it. Can you walk me through adding CUPS subsystem with the current landscape? I'll sit and wait. ;)
1 reply 0 retweets 2 likes -
Replying to @arcade_projects
I disagree, the linux in the mister is a tiny distro. If you want to run a printer off mister (CUPS?) then you might actually want a whole new distro with more of the functionality in pre-installed shared libs. Maybe a new DE10 linux distro is a worthy project?
2 replies 0 retweets 0 likes
"hen you might actually want a whole new distro" no what I want is to handle it like any other open source system, and not be gate kept by other folks desires.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.