Subject: Re: packaging a ripper front end, questions
To: David Brownlee <firstname.lastname@example.org>
From: Gavan Fantom <email@example.com>
Date: 05/16/2001 10:08:32
On Wed, 16 May 2001, David Brownlee wrote:
> /usr/pkg/share contains data files that are CPU/arch independent,
> I think mp3s probably qualify :)
Is /usr/pkg really the right place to be putting output from the script?
By means of a (slightly silly) comparison, you wouldn't expect vi to save
files in /usr/share by default. Or netscape to default to /usr/pkg/share.
Or INN to set up it's spool in /usr/pkg/share.
Maybe ~/mp3 (although I can see a lot of people running ripit.pl as root,
and /root normally lives on the root partition so this might not be so
good), just "mp3/" (relative to the cwd - works for me with this script),
"/usr/mp3" (It's where I personally tend to store mp3s, but probably not a
good thing to set as a default) or "/var/mp3" or "/var/spool/mp3"
> Can it read config from /usr/pkg/etc/ripit.conf and ~/.ripit.conf?
> (or be extended to do so :)
It's just a few perl variables at the start of the script so it should be
possible. That still leaves the question of defaults though. :)
Gillette - the best a man can forget