Subject: Re: packaging a ripper front end, questions
To: Gavan Fantom <email@example.com>
From: David Brownlee <firstname.lastname@example.org>
Date: 05/16/2001 11:29:20
On Wed, 16 May 2001, Gavan Fantom wrote:
> 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.
We have a /usr/pkg/share/httpd/htdocs. 'spool' implies transient
files, which I would hope my mp3s were not :)
> 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"
I would prefer one of /usr/pkg/share/mp3 ~/mp3 ./mp3
Thinking about it ~/mp3 probably makes the most sense.
> > 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. :)
David/absolute -- www.netbsd.org: No hype required --