On 06/27, Ralph Lange via Tech-talk wrote:
> On Thu, 27 Jun 2024 at 17:30, J. Lewis Muir <jlmuir at imca-cat.org> wrote:
> > Is the no-space-or-parentheses-in-paths restriction specific to Windows?
>
> See savannah.gnu.org/bugs/?712
>
> The workaround in the Windows guide is specific.
> I have rarely seen spaces in paths on other systems, while they're
> everywhere on Windows. (And brackets.)
The workaround is Windows-specific, but given the bug report you
referenced (which I just briefly skimmed), at least the no-spaces
restriction is not, so IMO that should be stated as a restriction in the
installation instructions for the other platforms. How common spaces
are in paths on other platforms seems irrelevant to me.
Lewis
- References:
- install epics-base: Perl Script Path Interpretation Issue on Windows Hussein Matar via Tech-talk
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows Johnson, Andrew N. via Tech-talk
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows J. Lewis Muir via Tech-talk
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Navigate by Date:
- Prev:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Next:
RE: Errors during building of asyn package Mark Rivers via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
<2024>
- Navigate by Thread:
- Prev:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Next:
Retrieve motor-record data from archiver appliance Heinz Junkes via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
<2024>
|