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: Sun, 10 Apr 2005 12:05:03 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Bertalan Fodor cc: John Sellers , cygwin AT cygwin DOT com, janneke AT gnu DOT org Subject: Re: lilypond-doc-2.4.3-1 using setup.exe 2.457.2.1 fails to display music images In-Reply-To: <42594ACF.6090108@freemail.hu> Message-ID: References: <4254A1CC DOT 5000009 AT sellers DOT com> <87br8o2wai DOT fsf AT peder DOT flower> <425898C4 DOT 5040604 AT sellers DOT com> <42594ACF DOT 6090108 AT freemail DOT hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 10 Apr 2005, Bertalan Fodor wrote: > Images are symbolic links. You won't see them but in cygwin. If the above directory is served by an http server compiled under Cygwin (e.g., apache), the symlinks will be resolved to real files. If, however, the files are opened by a Windows browser, the symlinks will not resolve to images. > Should I package them as files? (That would make a difference from the other > distributions.) What are the images symlinks to? Wouldn't it be better to just change the HTML file so that they refer to the images in the correct relative directory? FWIW, for Cygwin, it may be better to package the images as *hard* links, which will work on NT-based systems, and will cause setup to (correctly) produce copies on 9x systems. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/