forwarded 575642 ri...@suwald.com thanks * Serafeim Zanikolas [100328 19:30 +0200] > On Sun, Mar 28, 2010 at 05:55:54PM +0200, Elimar Riesebieter wrote: > > * Serafeim Zanikolas [100328 15:47 +0200] > > > On Sun, Mar 28, 2010 at 02:54:51PM +0200, Elimar Riesebieter wrote: > > > > Try > > > > $ cd /tmp && LC_ALL=C ripit -o $PWD --nointeraction > > > > > > I fail to see how's that related to relative pathnames, which is what > > > this bug > > > report is about. AFAICS $PWD is always set to an absolute path, so the > > > above > > > command will obviously work (same goes for ``-o $(pwd)'' > > > > $PWD points always to . (dot). The . isn't acceptet by ripit. See > > [0]. > > I'm not following. $PWD is always set by ``cd'' to the current directory, as > an absolute value. > > $ cd /tmp/ && echo $PWD > /tmp > > When a program advertises that a command line switch accepts a path, it is > assumed that such a path may be specified either as an absolute path (one > starting with a forward slash), or as value that is relative to the current > directory (one starting with a dot).
Plese tell me what the difference is between: $ cd /tmp && ls -al . and $ cd /tmp && ls -al $PWD ? > Saying that ripit doesn't support relative directories, doesn't make it less > of a bug. We can ask upstream to think about that > You may close this bug, you may document the fact in the manpage, but until > the bug is fixed, you'll keep getting bug reports like this one :) Two within 1 year isn't that much to manage ;-) Elimar -- You cannot propel yourself forward by patting yourself on the back.
signature.asc
Description: Digital signature
