Is it possible to run NeroLinux on Slack? I didn't download it yet because it comes in rpm or deb packages... I don't like those.



Then, let's suppose that it runs as smoothly as it comes... shall it be better than burning with cdrtools or cdrdao and k3b???

I just don't to waste my left empty CDR's

Peace

k3b should be better, but if you really want to use nero, you can use rpm2tgz to convert the RPMs.

doesnt nero cost money? i use the windows version of nero, and for me k3b provides equivalent functionality for what i need.

nero linux is only available as deb or rpm but rpm2tgz works just fine.

nerolinux runs perfectly but is only available in trial format and the current version time out on 31st august.

nerolinux works great for video & DVD, IME k3b cannot make so bold a claim.

Well, it's the full version that you download. If you don't enter a serial number the time bomb will take effect. I like using nero on Linux. Works like a charm. It's dog ugly using gtk1 but hey, atleast it works. And yea, rpm2tgz works just fine. After you convert it, you can explode it in a clean directory and add your slack-desc if you really want to.

It has a long way to go before it is a contender with K3B, but what functionality it does have at the moment seems to be flawless in my limited expierence so far. It's especially nice for Gnome users since it doesn't rely on KDE. Installing kde-{base,libs} just to use a K3B is pretty silly.

I don't think its silly to install kdelibs to just to use k3b. K3b is an official KDE package and relies on a lot of stuff in kdelibs. Its the same thing for gnome, I recently installed xfce4 on NetBSD and had to install some gnome libs to run certain apps even though I didn' want to run gnome. The thing with gnome is that it has a lot of cd burning apps under development, but so far none of them match the functionality of k3b.

Isn't it possible to only compile k3b with qt and not use kde libs. (im not sure).
I tried both nero linux and k3b and i think k3b is alot better.
But Nero also does what it's supposed to do.
So if theres not any feature u need that the other one got then it's just a matter of taste.
But Nero has lost my cdburner sometimes. (remember that Nerolinux is new so thats ok)
And if u got Nero for windows u can get the demo and register it with same serial. (needs serial 6.x i think).

No, k3b requires kdelibs (well on all distros I have used anyway).

what about xcdroast
it gives a graphical window, for cdrecord, nice one may b winblows users may like tht
just check http://www.xcdroast.org/#screenshots
get teh packages from http://linuxpackages.net/

Well, it's silly when you don't use KDE... KDE lumps everything into a few packages whereas Gnome has it's deps split up into a billion packages. If you only need 3Mb worth of libs from kde-libs to run K3B your stuck with installing 47Mb worth of stuff just for those few libs. You need kde-base as well... So now your looking at 97Mb just to run K3B... Not to mention QT is a dep. That puts us at 150mb worth of libs just to run K3B...That's a working KDE environment and lots of extra bloat just for a burning prog..... To me, that's silly.

I have found you only need KDE libs and QT to run any KDE based app. And it is not as bad as Gnome, which you really have to install the whole thing for any of the programs to run.

Right you are... For some reason I was under the impression kdebase was linked against. That's a little better.. I've been wanting to try and make a self-contained K3B that contains the deps too... Might be a worth-while endeavor.

If its statically compiled against KDE and QT, it should work if they are using the standard .so system. It might be that there are other things in those packages that are difficult to extract.

thank you all for your answers, but I shall stick to K3B, as long as I don't want to have any try-it-like-it-and-forget-about-it software in my machine LOL

I hadn't notice NeroLINUX was a trial.

As mentioned by others, you only need qt and kdelbs to run most kde apps. As for KDE lumping together everything into a few packages, thats not entirely accurate. You can build kde packages so that you only have individual modules/programs without building the whole package set. This approach is taken by Suse and Mandriva, who provide individual KDE packages instead of entire package sets.