> On Mar 25, 2025, at 4:45 PM, Stu via Freedos-user > <freedos-user@lists.sourceforge.net> wrote: > > There are two things I want to do - > > One is to create a package for Animator (which used to be known as Autodesk > Animator or AnimatorPro) > > I have a script I started here > https://github.com/stuaxo/animatorpro-fdpkg/ > <https://github.com/stuaxo/animatorpro-fdpkg/> > > At the moment this packages existing binaries, but I wouldn't submit this for > inclusion until I can actually build Animator, and work out what else needs > to be included, some sanity checking would be great. > > > I'm also interested in writing a script to make a package for TurboC++ 3.0 - > this couldn't be included, but I have a license for it, so would like it to > be reproducibly installed > for a dev environment, in that case I'd make the script that generates the > packages available. > > TurboC++ would want some environment variables setup + the PATH. > > > For the Borland tools that were released, I'd need to check if I could > package them, or if I'd need to do the same approach of download - then have > a script to package them.
I took a look at the the project. For the most part, everything looks good. The LSM looks fine and the directory structure for the ZIP looks correct. I’m sure you are away that several paths in the ZIP archive get remapped during installation. For example, the \PROGS\ANMATOR will be mapped to C:\ANIMATOR when installed by the package manager. To see a complete listing of the mappings that occur, check out the C:\FreeDOS\bin\fdnpkg.cfg file. I saw the LSM copying-policy shows copyright and not an open source license. It the project open source, freeware, commercial , etc? Unfortunately, it would need to be open source for consideration to included with a FreeDOS release, GitLab Archive or the Official Software Download/Update Repository. However, my Unofficial FreeDOS Download/Update Repository has all of the same packages as the Official repository. Plus, it is less restrictive and has more packages. As long as the license permits it can be legally redistributed in package form, it could potentially be included there. My server also has a few programs which are not open source that permit redistribution, but forbid modifications. For those, they are simple provided outside the repository under the https://fd.lod.bz/redist path as-is. The repository management software (used on both sites) does have an additional requirement which would need satisfied by your package. Even when there are no sources or if sources are included elsewhere in the package, there must be a directory for sources and at least one file present. In your case, a file SOURCE\ANIMATOR\README.TXT would satisfy the repository management software. That is a requirement of the repositories. It does not effect the package manager that installs/removes packages. :-) Jerome
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
