Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 28 Dec 2004 12:19:39 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: postinstall-lilypond.sh Message-ID: <20041228171939.GB5127@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Dec 28, 2004 at 11:02:20AM -0600, Brian Ford wrote: >Cosmetic note for maintainer: > >[snip] ># cleanup old fonts >rm $(find /var/lib/texmf /var/spool/texmf /var/cache/fonts -name 'feta*pk' >-or -name 'feta*tfm' -or -name 'parmesan*pk' -or -name 'parmesan*tfm') >[\snip] > >find: /var/lib/texmf: No such file or directory >find: /var/spool/texmf: No such file or directory >rm: too few arguments >Try `rm --help' for more information. > >Maybe add a -f to rm? That would eliminate one of the error messages. > >As for the directory errors from find, I'm not sure how to avoid >them without pre-testing for their existance in the script and >setting a variable appropriately. I understand that may add too much >complexity just to avoid a harmless error message. We shouldn't have post-install scripts which show errors regardless of whether they are harmless or not. There is no reason to surprise or confuse users if it can be easily avoided. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/