Date: Mon, 10 Apr 2000 08:52:30 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Richard Dawe cc: Laurynas Biveinis , DJGPP Workers , Richard Dawe , Zippo Workers Subject: Re: DJGPP library DSMs In-Reply-To: <38F08939.788D188E@bigfoot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 9 Apr 2000, Richard Dawe wrote: > > > 7) Perhaps the installer and uninstaller should automatically run > > > install-info with the appropriate arguments (these arguments are > > > pretty standard). This way, people won't need to put these > > > commands into the DSM files, which is error-prone. > > > > No, I think it is up to indvidual packages: installers should be > > generic, they don't know very good, which packages require it and which > > don't. > > I personally have mixed feelings about this. I still haven't used > install-info. I would prefer all actions to be taken on installation to be > included in the DSM. That way, one could install the package without a > package manager, by looking at the commands in the DSM. I agree with the goal, but I could also take it to the extreme and say that the unzip command should also be there--so that someone could install the package manually... I understand that we need to draw the line somewhere, the question is where. > Why is putting these install-info commands in the DSM error-prone? Because the command line will be written by humans, and humans tend to err. OTOH, the command itself is so standard that it cries for automation: install-info --info-dir=/dev/env/DJDIR/info --info-file= > I intend to write a DSM writing guide at some point. I could describe > running install-info in this guide. Is it worth to duplicate what the Texinfo manual already says?