delorie.com/archives/browse.cgi | search |
-: > > I probably lost my copy of `charset.alias' a frenzy of installation, -: > > hacking, and reinstallation. Perhaps (a version of) `charset.alias' -: > > should be included with any NLS-capable package? Here I should have said `included with the binary distro of any NLS-capable package'; once my charset.alias had been nuked, (re-)installation of sed3028b.zip did not restore it. -: 1) charset.alias is generated and installed by every GNU package that -: offers NLS *and* runtime recoding. IMHO this is the root of the problem; the resources for NLS and runtime recoding are bound with individual programs, and cannot (yet?) be packaged for separate installation (iff NLS support is desired). Thus removal of *any* NLS-aware package breaks the NLS-support for all remaining NLS-aware packages. -: 3) Including charset.alias and locale.alias in djdevNNN.zip will -: not really solve the difficulty, IMHO. I agree this is not a good solution; removing an NLS-aware package will simply remove whatever *.alias files are supplied with djdevNNN. -: 4) The simplest solution seems to be to omit charset.alias and -: locale.alias from the manifest file IMHO this is also not the right thing to do; it is an extra burden for the maintainer; it means the *.mft file is no longer a true package manifest; and it means that `rm -f @foo.mft' no longer does a complete job of removing a previous installation. Perhaps an `alias.zip' archive, containing only the *.alias files, should be packaged for independent download? (Not much of a solution, I know.) Or just do nothing (except to add *.alias to the binary distro) and see if it ever becomes a FAQ-level problem.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |