hi On Nov 2, 2024, at 3:29 PM, Fritz Mueller via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote:
This is regarding the Download/Update Repository. See below.
?
Perhaps it should be moved into a sub-directory and have its Batch Link file updated.
First, COMPUTE is not included in the release. It is currently an online only package. It is a bad idea to update packages and not update the package version for several. The primary reason is version identification. If a user already has a package installed and browses the HTML version of the Update Repository, they will see the version number and assume it has not been updated. Running FDNPKG to update the package will also not work directly. It will see that the version number is the same and also assume it does not require an update. The Repository itself should actually accept the package update because they are not actually identical. However, it becomes confusing for us humans when managing stuff. From the management standpoint, there are two possibilities. One… pull the existing package and replace it with the updated package. This is not a good solution because humans and software will not recognize it as an update. This is a long standing known problem. It is one of the primary reasons the Repository Management Utilities insert a Modified-Date field into the package metadata when added to a repo the first time. The intent being that the field will be used instead of the Version field for detecting and determining what gets updated. But, that is in the future at some much later time. Second, is to artificially bump the package number. Like BladeEnc 0.94.1 to 0.94.1a. But, this is also less than ideal. This was done to a lot of packages a long while back when numerous NLS updates was provided. It caused some confusion. So, Many of such had the version numbers restored to the actual program version when we started staging packages on GitLab. But, not all. Or, not in both locations. It is a very tedious and time consuming process to pull and replace packages in the download/update repositories. But simple to bump the version of a modified package. Bumping the version also comes with other issues. One of which is version numbering conflicts. For example, what if tomorrow there is a real bug fix update for BladeEnc that is version 0.94.1a. Like I said, there are good solutions planned. But, they will take a time fully roll out. Also, we are coming up on releasing FreeDOS 1.4 in the near future. Before that happens, a new 1.4 Download/Update repository will be created and config files provided in the release will be pointed at that repo. The repo will start with the package versions available on GitLab at release time. The 1.4 repo will probably be created and configuration adjustments sometime in the next few days. T2412 will point to the new repo.
Per the generated report and readme, a full install requires 325Mib. Full with sources requires 500Mib. Packages on the BonusCD are bonus packages and are not included in that size requirement calculations. Possibly the Readme could be updated to say something like “Installing packages from the BonusCD could require up to an additional 1Gib of storage space.” I don’t know where you got the “500 Gib is Standard” for an installation.
Jerome
|
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
