Hi Paul, You mentioned that you were having an issue with LFNFILES.ZIP file name collisions when installing multiple dj_* packages.
At present, there is no “good” solution to this. When the package gets extracted and long file name support is not present, the file names get truncated. This tends to break a lot of programs looking for those files. Likewise, even when LFNs are supported, those LFNFILES.ZIP just sit there. Again, tending to break programs looking for the files contained in that zip. Eventually… FDIMPLES will check for LFN support. When a package contains them, warn the user when LFN support is not active. If support is active, simply extract the nested LFNFILES.ZIP. Like multiple online repository support, it is on the “TO-DO list.” But, I’ve got to many other things needing done of higher priority. Unfortunately, updating FDIMPLES won’t help when using FDNPKG. Unless someone wants to improve it, you’ll be stuck with the nested LFNFILES archive regardless of LFN support. Possible solution to resolve your file conflicts. Look at the generated package file. Remove all of the LFN files it contains from the project on GitLab. Then add that LFNFILES.ZIP to the project under a new file name. Like LFNFILE2.ZIP. That way they can install to the same directory and not collide. :-) _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
