Since this is a 2.6.x aiming for newer hardware etc., is there a minimum machine spec target? This info might be useful for users who are compiling extensions so that they can use optimizer flags, etc.
fyi, I've had some problems with Felson's 2.10.9 extension though (for compiling stuff).
I had a giggle when lucky13 suggested "turf" - it is a good idea though. I'll just take something no one else has taken ;p Teams focusing on certain things might be good as well... (ensuring compatibility of their extensions etc)
Quote
does it have a complete toolchain?
I'll have to double-check, last time I used it was a version back but I recall it had everything. If not, it uses Debian-testing so it shouldn't be difficult filling in the missing pieces. We'll need Robert to provide more guidance first.Of course the murga incident affects this project as well. Who knows perhaps that was the real reason for the way in which it was handled; stop tinycore.
Many programs would need to be made into fltk only programs in order to continue. That will take some time. Or an alternate be suggested, or to use only command line version of the mydsl system and release anyway.I probably can't start til this weekend (Friday at the earliest), but I can get to work on a whiptail/dialog front end for mydsl if that's an acceptable alternative to FLTK or any other graphical took kit.My $.02 is that for now tiny core would be great with a command line environment for the MyDSL stuff until a replacement can be found. After all, if you cannot issue commands you will not be a good tiny core user anyway. I think the majority of DSL users would survive with it and it would be the quickest temporary replacement. And it can buy time for finding a toolkit while we are able to enjoy tiny core.
You know, the timing of that crap is indeed very unsettling.Next Page...
original here.