Why xcdroast and not gcombust?

[Erik Englund]

Hi,
The only time I switched back to Windows when i was a Linux newbie (and
didn't realize there was one thousand other burning apps for Linux) was
when i burned CDs. I really don't think that the average Linux user find
xcdroast the most useful CD burning app, and that's what you are
supposed to do, pick the best for us =)

//Erik

On Sun, 2003-08-31 at 23:10, Mike A. Harris wrote:
> On Sun, 31 Aug 2003, Steve Bergman wrote:
> 
> >I was just wondering why xcdroast gets included as the standard
> >cd writer and not gcombust.
> 
> Why not $ONE_OF_A_THOUSAND other CD burner applications?  
> Seriously, we can't ship every single application ever written in
> every application category.  We can chip one or two apps for most 
> important categories, but anything beyond that is distribution 
> bloat, and should be in a separate repository such as fedora or 
> another alternative repository, perhaps tied to the RHLP somehow.
> 
> By all means, file an RFE to have gcombust added to the 
> distribution, that's the normal way things get added.  There's no 
> guarantee it will get added automatically of course, but at least 
> it can be considered when we're investigating new packages next 
> time around.
> 
> >I always end up frustrated with xcdroast and gcombust is quite
> >friendly.
> 
> The xcdroast UI is not perfect by any means, but I find it quite 
> functional personally.  I've been using it since it was a TCL/TK 
> script.
> 
> >Also, it's obvious how to write an existing iso image with
> >gcombust and I don't see that xcdroast can even do it.
> 
> Well you're wrong there.  99% of what I use xcdroast for is doing 
> just that.
> 
> 
> >Plus gcombust fits in nicely with Bluecurve and is at least a
> >GTK app, whereas xcdroast is, well, whatever it is.  I there a
> >licensing issue or something?
> 
> Did you file a request in bugzilla?  If not, file it against the 
> "distribution" component.  If you know the email addresses of any 
> of the maintainers in the distribution of existing CD burning 
> packages, you might want to carbon copy them as well.  We 
> investigate user suggested packages submitted to bugzilla every 
> release.  Some of them get accepted, some end up replacing an 
> existing package in the distro, and some get rejected for one 
> reason or another.  It's best to have it in bugzilla however, so 
> it can be tracked.
> 
> 
> >Then again, eventually, I suppose, nautilus will do it all.
> 
> Nautilus already can burn CDs.
> 
> Hope this helps.
>