klange
commented
4 years ago Some thoughts on ports:
- I do want to collect more ports! We should focus on getting the things that were missed in the migration away from newlib - mupdf, mesa (a newer version, preferably), etc.
- We should avoid patchsets that just add stubs to the libc. I would prefer projects be undertaken to implement features if they are necessary, or the port should be properly configured to not use those features if they are not.
- I want to set up infrastructure so we can build ports automatically and turn them into packages. I also want to set up something so we can run tests against them. There's already a CI infrastructure in place for building base images of ToaruOS, we can use that as a base for building port packages.
Dennisbonke
I know that you probably have your own port collection somewhere but these are not available to the users, except for the packages on the package manager. I have added three ports in this pull request, which can be build after building and sourcing the toolchain manually by running the build.sh script in the directory of the port. zlib and ncurses required no additions to the libc but file wanted sigaction and the regex functions, which are stubbed.
Tested by recompiling everything and running the installed programs, ncurses6-config is a bash shell script and as such not working, and file complains about the magic database being invalid, which is strange as the same database works on my host. ncurses would like a terminfo file for the toaru terminal but is functioning otherwise. I am planning on more doing more ports later on as well as enhancing the build system used for the ports, as it is a tedious thing at the moment.
Feedback on this pr and whether you want me to continue porting software would be appreciated.