> On Nov 3, 2024, at 7:57 AM, Eric Auer via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > > Hi Jerome, > > thanks for the explanation that that updated package failed to > bump the version number. I would vote for an artificially bumped > version number as a workaround for now :-) > > Eric >
For the Interim Build and an actual Release, no version bumps are needed. The packages are put together by the RBE directly from the FreeDOS GitLab Archive. So, whatever versions and files are present in those projects are used for the install media. The FreeDOS 1.4 Download/Update Repository on ibiblio will contain those versions as well for it’s initial state. I’ve already updated the repo management config and created that repository. It contains the packages from T2411. All of which will be reset for T2412 and again each month until FreeDOS 1.4 is released. I have also update the different config files in various packages that are used to point the installed OS to that specific repository. I will need to make a local build before T2412 to insure I did not miss any settings. But, I think I’ve adjust all of the appropriate odds and ends. So nothing “needs” a version bump at this time. After 1.4 is Released, there will be package tweaks, NLS updates and minor changes that are not “version” updates. For the time being, I agree that the only practical solution is doing the artificial version bumps. However, we get a lot of NLS updates. Issuing a new package with a bumped version for every package that received an update to its NLS seems wasteful. While most users are speaking English and would be needlessly updating their entire package just for languages the cannot use, those NLS updates are very important to the users that are using those languages. I think going forward, NLS updates should not result in a package being updated on the Download/Update Repositories. Instead, an additional FDHELPER batch file could be created. Possibly called NLS-UPDT.BAT or NLSPATCH.BAT. The batch script could scan the NLS directory for the installed programs which have NLS files. Then connect to the FD-NLS project and download the latest version of the translations for each of those programs. Depending on which networking packages are installed, It would be capable of using HTGET, WGET or CURL. The batch should not actually very be difficult to write. Additionally, support would eventually be provided to perform the update offline. Possibly by downloading the entire FD-NLS as a zip archive then running a tool under FreeDOS to incorporate the changes. :-) _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
