> On Nov 11, 2015, at 1:50 PM, Mateusz Viste <[email protected]> wrote: > > On 11/11/2015 19:25, Jerome E. Shidel Jr. wrote: >> It seems kind time consuming for the FDI to run through every installed >> package with >> "FDINST remove” prior to doing an install. > > What do you mean by "time consuming" ? FDINST REMOVE won't do anything > if the package is not installed - it will execute only a check > determining whether or not said package is already installed. This is > something that needs to be done anyway.
Mostly, I mean going through all of the lists in batch logic. > >> Also, this would trash any packages that >> may have been installed from elsewhere. > > What is "elsewhere" ? I can't see a realistic scenario where FDINST > REMOVE leads to trashing something. Without going through a package list comparison and removal. Simply, removing all installed packages would dump files the user may have installed to a different directory that are not included in the FreeDOS release. The user would see it as having trashed there install of blahblah package installed in C:\MYTHING\. > >> Also, there is another issue. When installing a package if one of it’s files >> exist, the install will fail. > > It's not really an issue - that's a feature! :) FDINST won't install a > package if any of its file would collide with something already > existing. That's how it's supposed to be. I understand and that is fine, except…. > >> All of this would be solved with a simple /overwrite, /force or similar >> switch was added to FDINST. > > I'm really not comfortable with automated overwriting of anything. If > collisions are present, a human must be involved - otherwise the system > will start overwriting stuff that is likely to be used by something else > (first example that came to mind: overwriting data files of a program > that was installed manually, possibly mixing up several versions of the > same program). > > My opinion is that if collisions are found, installation of this one > package must be skipped, and optionally a warning message printed to the > user, so a carbon-based lifeform can sort this out (and that's exactly > how both FDNPKG and FDINST behave). An install or upgrade if installed option would be nice. It isn’t a conflict if it is upgrading a earlier version. :) > > Mateusz > > > ------------------------------------------------------------------------------ > _______________________________________________ > Freedos-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-devel ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
