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
-
-
Replying to @Bender65816 @Voultar
I don't seem to recall CentOS history being like that at all re: "since RHEL didn’t give it away" https://lists.centos.org/pipermail/centos/2004-May/000153.html … it was always a proper fork. See: https://en.wikipedia.org/wiki/CentOS pic.twitter.com/BdJBFLKEgu
1 reply 0 retweets 2 likes -
Replying to @arcade_projects
CentOS releases lagged RHEL releases because in each case the CentOS team had to create a working buildroot for the RHEL source, they didn’t get that from RedHat. Their fork had to be binary compat, so it wasn’t easy. For mister you’re talking about much less work.
4 replies 0 retweets 0 likes -
Replying to @Bender65816 @arcade_projects
Buildroot (tool) != rootfs(filesystem). CentOS lagged RHEL because it relied on it's community to patch and test the packages before pushing to the package manager repo. A RHEL license would get you the professional support for that
1 reply 1 retweet 4 likes -
Replying to @marcusjordan @Bender65816
I love how assertive he tried to sound with his claim. Lol. Like nah bro, that isn’t a thing. Nor was it ever.
1 reply 0 retweets 3 likes -
Replying to @arcade_projects @Bender65816
It circle backs to the Open Source LARPing. It's the principle of FOSS people don't get it. Is like ExxonMobil claiming that they're a clean energy company just because they have a few wind turbines and solar panels.
1 reply 1 retweet 4 likes -
Replying to @marcusjordan @arcade_projects
I’m not sure what your ultimate goal is but for the record I think forks are inevitable and the buildroot will not be an obstacle for long. Its a small embedded linux distro, not that hard to make same or similar with more support for stuff like CUPS if that’s what you want
2 replies 0 retweets 0 likes -
Replying to @Bender65816 @arcade_projects
idk if that's directed to me, but I already solved all that puzzle more then a year ago, you can even see the timestamp on the busybox config file. I already made a hard fork and spent a good time refactoring and cleaning the spaghetti code that Main is.
1 reply 1 retweet 1 like -
Replying to @marcusjordan @arcade_projects
Congrats on the hard fork, that seems like the right path to add things that the main project doesn’t seem to care about. Personally I think cast seeds and let a million forks bloom. Users will decide what is a good final product.
2 replies 0 retweets 0 likes -
Replying to @Bender65816 @arcade_projects
People doesn't even need to take my word or anyone for that matter. There are tools to exclusively deal with this: https://www.fossology.org/ and https://spdx.dev/resources/tools/ …. SPOILER ALERT: No repo will clear compliance. See if you can find any of this information attached on Main.pic.twitter.com/qo6NwhTy73
1 reply 1 retweet 2 likes
Lol @buildrootorg's "make legal-info" being one of them specifically. Why @alexey_saarsoft refuses to use it, is beyond me! Having @sentientsixp cheering him on doesn't help of course. ;)
https://buildroot.org/downloads/manual/manual.html …pic.twitter.com/M4LHsdelUb
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.