[Top][All Lists]

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

Re: sys_lib_search_patch_spec/path_separator (Re: Suggested pathes to CV

From: Gary V. Vaughan
Subject: Re: sys_lib_search_patch_spec/path_separator (Re: Suggested pathes to CVC libtool: Mingw improvement, .rc support)
Date: Tue, 25 Sep 2001 19:08:48 +0100
User-agent: Mutt/

On Sun, Sep 23, 2001 at 05:44:40PM +0200, Guido Draheim wrote:
> "Gary V. Vaughan" wrote:
> > 
> > On Sat, Sep 22, 2001 at 11:15:43PM +0300, Tor Lillqvist wrote:
> > > The chance of a Unix system having
> > > directory names containing semicolons is practically nil, isn't it?
> > 
> > Yup.  It is possible technically, but anyone who uses semicolons in
> > PATH has got to expect trouble, no?
> > 
> I think we agree. Now, I wonder if we would be so frank to just
> nuke the $path_separator thing and just go over to use *only*
> this generic heuristic about ';' occuring pathnames.

I'm game :-)

> Here's an example patch on top of libtool-1-4 ... which has the
> original code before we started to mess around with $path_separator.
> Otherwise it would again be needed to ensure path_separator is set.
> (the 1-4 lt_cv_sys_path_separator is always ':' but on djgpp)

But not on branch-1-4, which is purely in bugfix mode.

> for the 1-5 branch, we do make some assumptions about the help of 
> autoconf anyway IIRC, but again we might just go and use the 
> generic path_seperator detection for sys_lib_search_path as well.

I think it is definitely worth a try on the HEAD branch.  If we get it
in before 1.4d, and there isn't a huge commotion about stuff breaking,
then you are definitely on to something.

  ())_. Gary V. Vaughan     gary@(|
  ( '/  Research Scientist       ,_())____
  / )=  GNU Hacker  \'      `&
`(_~)_  Tech' Author   =`---d__/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]