I expect that all of the binaries and source are up to date at the time they are packaged, and that is a large effort - thank you!
But some projects are still active and move independently of FreeDOS. mTCP (my project) is one such example, and with years between the FreeDOS releases the binaries get stale fairly often. There isn't much that can be done about the binaries getting stale, as a distribution is a snapshot of what was available at the time. But I'd love to find a way where FreeDOS doesn't have to take responsibility for shipping source code too. For active projects it's much more desirable to mirror the source code that matches the shipped binaries, but to refer people to the current source code, not a historic snapshot of the source code. I'm trying to fix the binary staleness problem by including a small utility that people can run to see if they are up to date. I don't really know how to solve it for the source code, other than for just to plaster use warnings on the source code letting people know that it is probably out of date already. And that seems sub-optimal. Help me understand the GitLab environment for something like mTCP - is it just repackaging the binaries and source that I provide on my web site, or is it going further to recompile things? (I used to know this but I have my hands full enough with mTCP ...)
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
