Re: loginfo %s question

[Emile Snyder]

On Tue, 20 Nov 2001, gabriel rosenkoetter wrote:
> 
> Typically, something like (in Perl):
> 
>   $_ = shift @ARGV;
>   my @files = split;
>   my $dir = $cvsroot . "/" . shift(@files);
> 
> would be enough to get the right stuff out on your end, but that
> doesn't fix the problem you're seeing.

That is (in spirit) exactly what log_accum does...

> > Am I missing something?  Does anyone have any suggestions as to how to
> > parse the output of %s from loginfo into a directory part and a filename
> > part in a general fashion?
> 
> That's an ugly problem, and the only (clear and easy) answer I can
> give is, "Don't do that."

:)  Ah if only it were so easy...

> Spaces in a Unix-like OS's file system are not handled particularly
> well under many circumstances (say, um, any shell), making them a
> generally bad idea.

Yeah.  It's a case of making the tool fit the current situation.  We've
got some Windows only code under cvs control where the initial projects
were created with normal windows directory names (ie some had spaces).
Till now it didn't matter; only ever dealt with the projects on windows.  
But the loginfo scripts run on the server, so they've gotta handle the
naming in our current projects.  <dream>Someday maybe I'll get to clean up
the repository. </dream>

thanks,
-emile

> 
> -- 
>        ~ g r @ eclipsed.net
>