Hey, Okay I created a merge request. There wasn't actually a separate LSM page, but I included your description from your reply.
https://gitlab.com/FreeDOS/docs/-/merge_requests/4 Please review and LMK if something needs a rewrite :) --Wolf -- |\_ | .\---. / ,__/ / /Wolf <wolf+...@bergenheim.net>_ On Wed, Mar 26, 2025 at 6:55 AM <jer...@shidel.net> wrote: > LSM field changes and additions off the top of my head: > > Most fields are not required. Only the Title, Version, Description, > Copying-Policy are mandatory. > > - Description: a very very short description > - Summary: A much longer summary of the package. It can be > very long and include things like features, requirement and other > information. > - Primary-site: Current developer URL > - Alternate-Site: Mirror URL or other such location > - Original-Site: The original website > - Wiki-site: Usually a link to our Wiki for the program. Could > point to some other URL for help. > - Entered-date: YYYY-MM-DD usage varies. Generally, it is the last time > the program was updated. However, that is not enforced in any way. Only the > format is enforced by the repository management software. > - Modified-date: YYYY-MM-DD.N is the last time the package was > updated. It can be added/updated by using the new FDVCS -mod option. If > this field does not exist, it will be added by the repo management software > at that time using the current date. The N is a value of 0-9 and it will be > used if multiple versions are released on the same day (like recently with > XCOPY). In future versions of programs like FDIMPLES this field will be > used instead of attempting to compare version numbers to determine the > newest version of a package. > - Changes: An unimportant and rarely used field. If it > exists, it can highlight what improvements over the previous version has > been performed. The repository management software will include this > information when generating an RSS feed. > - Long-file-names: true or false. If the package has long file names > anywhere outside of the program sources. Future versions of programs like > FDIMPLES will look for this field and warn the user if LFN support is not > enabled. They will likely also automatically extract any LFNFILES.ZIP that > is embedded in a package when LFN support is enabled. This field can be > easily updated using the -lfn option of FDVCS. > > Note: In the past, when a URL no longer points to a valid page, the entry > often get’s prefixed with Defunct-*. For example, the original website no > longer exists and we do not want it displayed on various web pages. But, we > want to keep the URL in the LSM file for a reference. Storing it as > Defunct-Original-site accomplishes that. Not sure if that should continue > or not. > > Translation LSMs: > > These files go into the same directory as the primary LSM using a file > extension based on the DOS language code. They are used by programs like > FDIMPLES and PKGINFO to display package information in the users preferred > language. Only the fields which need translated should be included (plus an > additional required field). Only the following fields should be present and > will override the English versions in the LSM. > > - Language: Mandatory field. LANGUAGE_CODE, CODE_PAGE, > COMMENT. For example: “Language: DE, 850, German (Standard)” > - Description: Optional, translated description > - Summary: Optional, translated summary > - Keywords: Optional, translated keywords > - Title: Avoid translating the package title. > > :-) > > Jerome > > > > > >
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
