Well, I can agree with you to a certain extent. I wouldn't use whitespace in any of my projects files. However I'm packaging Digikam, one of the shining stars of the open source world IMHO. And it includes a few files with white space in the names, files designed for humans, not computers or programmers like us. Bottom line is I can't package it unless I do something far worse than white space in file names.
PS, thanks for the reply... and for the great software that got me into debian packaging. I use equivs-build to package for PCLinuxOS too. I found it easier to make a simple deb and alien it rpm than to figure out how make a simple rpm. Thomas Koch <tho...@koch.ro> wrote: >Euan Thoms: >> I started hacking a solution to the white spaces in files names. I got it >> working for the equivs-build script but then hit a wall when I discovered >> that dh_install itself does not support white-space in file names / paths. >> The issue was raised in 2003 and basically the maintainer is not >> interested in resolving the situation. I find it quite disturbing and >> unacceptable that we can't have white-space in file names for core >> packaging tools. Is there something I'm missing here? How can this stay >> like this for nearly a decade? >I can't help but smile and consider it a wonderful feature that the core >packaging tools shield my system against files with whitespace... :-) > >Thomas Koch, http://www.koch.ro
