> The standard routine here is to commit first to trunk and then forward the > lyx-cvs e-mail, with the patch, to lyx-devel asking for comment and > permission to commit to branch. I'll be happy to accept more such fixes if > they aren't too dangerous.
But trunk development is on git now? And due to the ease of branching, I understand that, do to the ease of branching on git, the people with commit access to the main git repo is limited, so I can't do this myself. In any case, would someone like to commit the attached patch, by Pino and adapted by Sven? This patch has the approval of me and Enrico Forestieri [1]. I am not sure if we want to rush this in before 2.0.1, but the new executable code is all hidden within an #ifdef that should only be triggered on systems where LyX would otherwise not compile at all (i.e. GNU/Hurd). My suggested log entry: Fix bug #7467: Allows LyX to build on systems that do not define PATH_MAX, such as GNU/Hurd. This fix by Pino allows unbounded path length when PATH_MAX is not defined, as suggested by the GNU coding guidelines. [1] http://www.lyx.org/trac/ticket/7467 -- John C. McCabe-Dansted
path_max.diff
Description: Binary data
