tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: spaces in PLIST

On Fri, Mar 14, 2014 at 12:42:55PM +0000, Jonathan Perkin wrote:
> * On 2014-03-14 at 12:33 GMT, OBATA Akio wrote:
> > devel/py-setuptools/PLIST has following (space in paths):
> > 
> > ${PYSITELIB}/setuptools/script template (dev).py
> > ${PYSITELIB}/setuptools/script template (dev).pyc
> > ${PYSITELIB}/setuptools/script template (dev).pyo
> > ${PYSITELIB}/setuptools/script
> > ${PYSITELIB}/setuptools/script template.pyc
> > ${PYSITELIB}/setuptools/script template.pyo
> > 
> > Is it supported in whole pkgsrc?
> Yes, lots of packages have filenames with spaces:

While pkgsrc tries to support filenames with embedded spaces, pkgsrc
uses make(1) for a lot of its processing and make definitely does not
support spaces in filenames.

There is a lot of cruft in the pkgsrc makefiles that uses \ to escape
spaces. A lot of the time this works because make doesn't treat the
\ special in any way - so it gets processed by the shell when the command
is executed and all appears to be well.

There are one or two places where make will treat \ as quoting the
next character - but they are very specific constructs.

If you get make to dump its internal symbol table while running the
pkgsrc makefiles you'll find make variable names that end with a \.
Clearly the intent was to generate a variable name containing a space
character - but that wasn't the effect.


David Laight:

Home | Main Index | Thread Index | Old Index