And just to add... all of the other packages that people would prefer removed.

Jacob

And just to add... all of the other packages that people would prefer removed.


Edit: Ok... I should check the dates of comments before I reply.

Jacob

What i really like sometimes is ability to use italian slacky repositories with gslapt to quickly install multimedia software which commonly have dozens of dependencies and would be pain to compile even with sbopkg.

So my wish is just to make precompiled _SBo packages available somewhere also, as i presume they are being compiled anyway on a clean slackware system during the testings of a slackbuild.

And on another note i think kde4 version of k3b on -current should go to 'testing' so people can test if it will even work. And maybe there is some replacement (lightweight)(GTK?)burner software to go to main tree.

Cheers!

I would vote for recorder: http://code.google.com/p/recorder/
But i seriously doubt that leaving k3b out of kde/ is a solution.
Maybe the solution would be to upgrade it to some later version than the one now, and keep updating it after the release, even if its not a security update.

Emacs-23.1
http://lists.gnu.org/archive/html/em.../msg01526.html
http://emacs-fu.blogspot.com/2009/07...very-near.html

Looks nice, that little recorder app. I've written a SlackBuild for it here, in case anyone's interested: ftp://ftp.noc.soton.ac.uk/pub/pwc101...ystem/recorder

Once SlackBuilds.org is accepting submissions again, I'll submit it.

I agree. Although, it's not that difficult to modify the emacs.SlackBuild script in the source directory to build emacs 23.1 and upgrade the package.

That one reason I'm thankful that Slackware includes not just the source, but also the tools to build packages from the source.

Regards,

Yes, I could try that. Then I might have to blacklist it in slackpkg so it doesn't get "down/up-graded".

I've been meaning to do that myself but your scripts are SBo ready, so no need for that anymore.
I think it would be a very useful addition to SBo. Since graveman is unmaintained.

Thanks for info about recorder, thanks for the slacbuild also! (Good) K3b had just been failing me again, this time with data cd, i guess it is just not ready yet.

edit: Was rejoicing too early, recorder doesn't cut it too. I ended up with an empty /bin - :-D - i have only myself to blame i guess.

Many of the SlackBuild maintainers already do this. Check out http://www.slackwiki.org/Writing_A_S...t_Repositories. Not all of the SlackBuilds are SBo, but many are.

Keep in mind, however, that for some software you may want to use special build options or dependencies, so using precompiled packages will not always work for you.

I've come to realize the whole issue with binary repository vs compiling is more complicated than it may seem to regular user like me.
Maybe slackbuilds.org could just package sbopkg queue files along with slackbuilds and make them available through sbopkg program interface(?).

It's a valid point, though.

Question, to those that know: if I don't install the HAL packages, is that going to cause major problems? I'm not sure what it's used by, apart from KDE for automounting (which is why I don't use it). I don't let rc.hald execute on boot and haven't noticed any problems.

I do not think that SBo would host queue files as they are intended for sbopkg, which is a third party tool. SBo does not change things for sbopkg. Rather sbopkg is a convenience tool for people to use SBo. However, the sbopkg team may be willing to host those files on their site. If nothing else, I'm sure people will post them to the sbopkg and/or SBo mailing lists.

That's a good idea.

Instead of going to slackbuilds.org, and grabbing lame, faac, faad, x264, xvidcore ...... download, build, rinse, repeat, just download a single sbopkg build queue for ffmpeg.