Subject: Re: packaging a ripper front end, questions
To: Tracy J. Di Marco White <>
From: David Brownlee <>
List: tech-pkg
Date: 05/16/2001 17:46:50
On Wed, 16 May 2001, Tracy J. Di Marco White wrote:

> David Brownlee wrote:
> }On Tue, 15 May 2001, Tracy Di Marco White wrote:
> }
> }> I've been playing with for a while, and have been looking at
> }> packaging it up.  It's got a few too many options, it allows you to
> }> use cdparanoia, cdd, tosha, cdda2wav to rip CDs, I'm going to depend
> }> on cdparanoia.  It uses bladeenc, lame or gogo to encode from ripped
> }> files to mp3s, I'm going to depend on lame.  I don't know if this
> }
> }	You might want to have RIPIT_USE_XXXX conditional options in the
> }	Makefile.
> I was not sure about doing that, since I thought it implied adding things
> to mk.conf, and I thought that was something to avoid?
	Have it default to something sane, but can be overridden at
	compile time, and ideally at runtime also.

> I'm 'extending' several bits of it, I could probably do that.  One of the
> things to consider is that while mp3 are small (1MB - 24MB for mine),
> the ripped files are also going into this directory, and tend to be 10x
> the size of the final mp3.  When I first started using ripit, it was
> putting them in /tmp, which filled up very quickly.  A user can end up
> with an entire ripped CD in this directory, around 640MB or so.  Fair
> warning may be considered sufficent, of course.
> Alistair Crooks wrote:
> }Personally, I'd make it "." - but what do I know?
> I can do that.  All mine go in /usr/music, but as Gavan wrote, probably
> not a good thing to set as a default.

	After switching on my brain I'd definitely have to agree with
	Al :)

		David/absolute		-- No hype required --