Subject: Re: packaging a ripper front end, questions
To: Gavan Fantom <firstname.lastname@example.org>
From: Alistair Crooks <email@example.com>
Date: 05/16/2001 12:06:29
On Wed, May 16, 2001 at 11:42:07AM +0100, Gavan Fantom wrote:
> On Wed, 16 May 2001, David Brownlee wrote:
> > We have a /usr/pkg/share/httpd/htdocs.
> Yes, but that directory contains files that are put there for apache to
> use, rather than put there by apache.
> > 'spool' implies transient files, which I would hope my mp3s were
> > not :)
> There is that. ;o)
> > I would prefer one of /usr/pkg/share/mp3 ~/mp3 ./mp3
> > Thinking about it ~/mp3 probably makes the most sense.
> If you log in as a normal user then su to root, ~/mp3 will still point to
> /root/mp3, won't it.
> Is there something that would maybe be based on LOGNAME? Or is that going
> Gillette - the best a man can forget
What I don't understand about this whole question is:
why does the ripping/encoding script need to be told where to put
the resulting mp3s? Surely it should be the cwd?
Personally, I'd make it "." - but what do I know?