From: Beni C. <cb...@us...> - 2004-05-15 20:19:46
|
Currently, symlinking a config file to another directory breaks the interpretation of the relative paths contained therein (like `stylelesheet_path` and pep_html's `template`). Suppose you have ``foo/docutils.conf`` containing:: [pep_html] template: pep-html-template and ``bar/docutils.conf`` is a symlink to ``../foo/docutils.conf``, processing a PEP in ``bar/`` will break -- unless ``bar/`` contains it's own ``pep-html-template`` file. I'm pretty sure that the Right Thing is to interpret relative paths relative to the realpath of the config file. The later interpretation (``bar/pep-html-template``), might sometimes be useful but is always achievable by copying the config file. So unless anybody speaks for it, I'm going to check in a half-line fix that uses the realpath. [Yes, I know this all is barely required because you can explicitly specify the same config file when working in different directories; nevertheless symlinking is sometimes more convenient because it avoids the need to specify ``--config`` correctly. Notably, if you have several configs, each affecting several directories, symlinking is the only sane way to make ``buildhtml.py`` behave well.] -- Beni Cherniavsky <cb...@us...> Note: I can only read email on week-ends... |