LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 08-10-2009, 05:08 AM   #736
pwc101
Senior Member
 
Registered: Oct 2005
Location: UK
Distribution: Slackware
Posts: 1,847

Rep: Reputation: 128Reputation: 128

Quote:
Originally Posted by disturbed1 View Post
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.
The upcoming release of sbopkg (0.30.0, I think) will include a set of sample queue files to do just this. I've submitted a few to the development team, as well as the 6 or 7 they already have. Thus, if you install sbopkg with the next release, you'll get a bunch of queue files to build some complicated packages.

If you're feeling that way inclined, you could write some yourself and submit them, they're not particularly complicated. Here is a monster one for all the multimedia-type applications at SBo:
Code:
######################################################################
# Unofficially suggested build order for almost everything that is
# AV/DVD related at SBo. After all of this, k3b #should support
# reading/ripping CSS DVDs, DVD creation with menus, and VCD creation.
# MPlayer will support quicktime #and reading encrypted DVDs,
# k9copy/avidemux2/kino/audacity will have nearly have a full set of
# encodings supported as well. This is only a suggested build list and
# order and is not directly endorsed by slackbuilds.org or sbopkg.
# YMMV.  Courtesy of antiwire
######################################################################
a52dec
aften
amrnb
amrwb
libmp4v2
faac
faad2
lame
libavc1394
libdca
libiec61883
libmpcdec
libmpeg2
libsamplerate
libsndfile
twolame
openjpeg
mjpegtools
schroedinger
speex
soundtouch
xvidcore
yasm
x264
divx4linux
libdvdcss
dvdauthor
libdv
libdvbpsi
#current/13.0 includes the next
libdvdread
libdvdnav
libdvdplay
vcdimager
vobcopy
ffmpeg | AMRNB=yes AMRWB=yes
libquicktime
transcode | MJPEGTOOLS=yes
mplayer-codecs
# current/13.0 includes the next but lacks libdvdcss support and
# codec package.  Rebuild for CSS required.
mplayer
kino | QUICKTIME=yes
avidemux | QT4=yes
k9copy
wxGTK
audacity
Options to pass to the build scripts are separated from the package name by a |. Packages can be omitted by prefixing them with a -. You can also call another script within a script using the syntax:
Code:
# Some queue file for sbopkg
@ffmpeg_build    # this calls an sqf file called ffmpeg_build
-audacity        # this would be omitted due to the preceding -
motion
In addition, a new switch (-k) added to sbopkg in SVN means that any packing which is currently installed can be skipped (no check will be made to see if there are any updates to this packages though). So, calling sbopkg as follows will build and install all the packages in the sqf file, but will not re-build packages already installed on the system:
Code:
sbopkg -k -i /var/lib/sbopkg/queue/ffmpeg_build.sqf
This functionality is not available in the ncurses-based menus.
 
Old 08-10-2009, 08:53 AM   #737
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,971

Rep: Reputation: Disabled
Quote:
Code:
# current/13.0 includes the next but lacks libdvdcss support and
# codec package.  Rebuild for CSS required.
mplayer
This is actually not necessary -- libdvdread does a soft dlopen() for the libdvdcss libraries, so simply installing libdvdcss is enough.
 
Old 08-10-2009, 09:00 AM   #738
pwc101
Senior Member
 
Registered: Oct 2005
Location: UK
Distribution: Slackware
Posts: 1,847

Rep: Reputation: 128Reputation: 128
Quote:
Originally Posted by rworkman View Post
This is actually not necessary -- libdvdread does a soft dlopen() for the libdvdcss libraries, so simply installing libdvdcss is enough.
Ah, that's handy

I'll let chess and the gang know and they can modify the queue file to reflect that.

As an aside, I was trying to build dvdbackup last week and noted that the version of libdvdread (Mplayer's, as opposed to Ogle's) in -current won't allow dvdbackup to compile. There is a patch on their site, which when added to the SlackBuild for current's libdvdread will allow dvdbackup to build.

I don't know what the policy on including patches in stock packages is when those patches aren't necessary to get Slackware working, but thought I'd mention it nevertheless.

I was tempted to email Pat, but thought he's probably got enough on his plate at the moment.
 
Old 08-10-2009, 09:05 AM   #739
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,971

Rep: Reputation: Disabled
I *seriously* doubt he'd apply a third-party patch to libdvdread for that. One never knows though :-)
 
Old 08-10-2009, 09:07 AM   #740
pwc101
Senior Member
 
Registered: Oct 2005
Location: UK
Distribution: Slackware
Posts: 1,847

Rep: Reputation: 128Reputation: 128
Quote:
Originally Posted by rworkman View Post
I *seriously* doubt he'd apply a third-party patch to libdvdread for that. One never knows though :-)
That's what I thought, and why I didn't bother him about it.

It's easy enough to recompile libdvdread to include the patch, so I think I'll leave it at that
 
Old 08-11-2009, 03:15 AM   #741
shotwellj
Member
 
Registered: Jul 2005
Location: Tempe, AZ
Distribution: Slackware
Posts: 66

Rep: Reputation: 15
lightweight office suite... siag office?

I stopped using KDE and basically all of this KDE4 nonsense. This isn't a Slackware thing, I just don't find KDE4 stable/usable/et cetera. Personal preference.

Additionally, I have found myself on a slower computer because my old one is currently broken. Occasionally I have the need for a word processor and I very frequently have the need for a basic, but not rudimentary, spreadsheet program.

I turned to my old friend siag, which I propose should be included even if it is trivial to compile.

Sorry for two edited posts in one thread, this one was due to a misfire on "submit reply". I'm on a laptop with broken keyboard/touchpad.

Jacob

Last edited by shotwellj; 08-11-2009 at 04:17 AM.
 
Old 08-11-2009, 08:26 AM   #742
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,658
Blog Entries: 3

Rep: Reputation: 224Reputation: 224Reputation: 224
Quote:
I stopped using KDE and basically all of this KDE4 nonsense. This isn't a Slackware thing, I just don't find KDE4 stable/usable/et cetera. Personal preference.
I under stand what your saying. I finally took my old 1200 mhgz machine and passed it on. I have a dual amd core 2.8 ghz machine with 2 gigs of ram.
KDE4 is very stable on slack64 I find it very simple and many tools for navigating.
there is just an endless amount of personnel set ups.
I have to agree that the old machine made the big ram eater KDE4 lethargic but never unstable in slackware.
I go back and forth with KDE3 and KDE4 after some use I find kde4 is really growing on me. Just MY Personal preference
 
Old 08-11-2009, 07:18 PM   #743
shotwellj
Member
 
Registered: Jul 2005
Location: Tempe, AZ
Distribution: Slackware
Posts: 66

Rep: Reputation: 15
Quote:
Originally Posted by Drakeo View Post
I under stand what your saying. I finally took my old 1200 mhgz machine and passed it on. I have a dual amd core 2.8 ghz machine with 2 gigs of ram.
KDE4 is very stable on slack64 I find it very simple and many tools for navigating.
there is just an endless amount of personnel set ups.
I have to agree that the old machine made the big ram eater KDE4 lethargic but never unstable in slackware.
I go back and forth with KDE3 and KDE4 after some use I find kde4 is really growing on me. Just MY Personal preference
There seems to be a wide gap between the "it's stable" and "it's completely unstable" crowds. My guess is that those who find it unstable have a need for some rather particular functionality. I have no doubt that these will eventually be cleared up. Additionally, some apps have yet to be ported to KDE4 or have ports in a very alpha state. Again, I'm sure it'll all be cleared up. It just comes across as completely unusable when things start crashing without any explanation after 30 minutes of usage.

What sort of bugs? Kile, for example, crashes when I try to do certain search/replaces with regular expressions, but hey, vim+vim-latex is much better anyhow. Or, for example, I recently discovered that kopete crashes immediately when trying to configure a webcam (4.2, 4.3... across distros).

Even when it's stable for me, I just don't like it (e.g. dolphin). Some people don't like tomatoes --- it's pretty much the same sort of dislike. No matter, I'm currently having more fun configuring my own desktop solution --- so no worries.

Jacob
 
Old 08-12-2009, 09:37 AM   #744
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 2,658
Blog Entries: 3

Rep: Reputation: 224Reputation: 224Reputation: 224
I would like to see a little more suport for webcams.Suport would be just a little more updated info in Documents. The kernel keeps changing and the drivers are becoming part of the Maintained kernel.
Quote:
discovered that kopete crashes immediately when trying to configure a webcam (4.2, 4.3... across distros)
. this crash is actually a 64bit problem I have with slackware it is not a KDE4 problem. If 32bit grab the package at slackbuild.org and install it and edit your launcher to preload the v4l1compat.so.
Quote:
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so kopete
for 64bit you need to get the source and I install it to default /usr/local/lib/ because I just want to keep it seperate from my other stuff. I use amsn and gyachi and I launch them like this.
Quote:
LD_PRELOAD=/usr/local/lib/libv4l/v4l1compat.so gyachi
this loads the /usr/local/lib/libv4l/v4l2convert.so library that converts v4l1 to be used worth the v4l2 driver that comes with the kernel.
 
Old 08-13-2009, 10:13 PM   #745
salemboot
Member
 
Registered: Mar 2007
Location: America
Distribution: Linux
Posts: 160

Rep: Reputation: 36
Gap indeed,


Some interesting observations:
1. krandr has to be loaded in the task tray to keep your settings for external LCD's.

2. KDE developers have yet to implement the background effects like blending in plasma.

3. Even with desktop effects disabled in KDE4, OpenGL performance suffers on my system.

4. CPU Frequency scaling is broken for Sony laptops, don't know about the rest of you guys. Had to manually set /sys/..../cpu0 and cpu1 to Performance. Which brangs me to another issue on the intel front. Prior to xf86-video intel 2.8, there was a bug with cpu scaling crippling performance. You'll get this in 2.7.x.



Quote:
Originally Posted by shotwellj View Post
There seems to be a wide gap between the "it's stable" and "it's completely unstable" crowds. My guess is that those who find it unstable have a need for some rather particular functionality. I have no doubt that these will eventually be cleared up. Additionally, some apps have yet to be ported to KDE4 or have ports in a very alpha state. Again, I'm sure it'll all be cleared up. It just comes across as completely unusable when things start crashing without any explanation after 30 minutes of usage.

What sort of bugs? Kile, for example, crashes when I try to do certain search/replaces with regular expressions, but hey, vim+vim-latex is much better anyhow. Or, for example, I recently discovered that kopete crashes immediately when trying to configure a webcam (4.2, 4.3... across distros).

Even when it's stable for me, I just don't like it (e.g. dolphin). Some people don't like tomatoes --- it's pretty much the same sort of dislike. No matter, I'm currently having more fun configuring my own desktop solution --- so no worries.

Jacob
 
Old 08-17-2009, 09:30 AM   #746
AGer
Member
 
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Blog Entries: 22

Rep: Reputation: 19
I wrote something like the following in another thread, but now, looking at the system upgrading to JDK 6u16 and thinking if I should stay on -current or go 13.0, I guess it may be worth the effort to restate it here.

There are packages that I believe are very much out of Slackware control being developed by well respected upstream teams, like Sun JDK, Firefox, Ruby, Python, PHP, and so on. Currently the latest versions of such packages appear either in -current or on Slackbuilds. I guess it would be nice to have them in /extra of the stable branch, at least those that appear in -current anyway (that is, JDK and Firefox but not Ruby 1.9 and Python3).

My humble guess is that this may require a change to slackpkg so that it knows when to use a package from /extra and when from the main tree, while creation of the packages can be automatic and just a side effect of compiling them for -current.

It is not necessary to test such packages since if there are problems they should be considered upstream problems, not Slackware ones. Slackware does not create JDK or Firefox patches, it just packages "as is".

Currently, as far as I can see from the change logs, 12.2 has Firefox 3.0.13 while -current has firefox 3.5.2; 12.2 has JDK 6u11 while -current has JDK 6u16. In plain user words, -current is current and stable is outdated.

JDK is a perfect example why this is not OK. The practice I commonly observe whenever Java is actually in use is to test existing software with each JDK release and, based on the results of the tests, upgrade or stay. That is, there is no "right" JDK version that should be included with a distribution and it is not correct to say that 6u11 is in stable since it is well tested while 6u16 is not well tested and thus is only in -current.
 
Old 08-18-2009, 09:11 AM   #747
vonbiber
Member
 
Registered: Apr 2009
Distribution: slackware
Posts: 299

Rep: Reputation: 50
a sensible vi

it took me a while to figure this out
but now whenever I install a new version of slackware
that's the first thing I do:

set the display:normal as default for html and tex files
in the elvis config files

I don't like this behavior a la emacs.
vi is an editor, period. I use it to edit code so I expect
to see my code there.

Hope also we'll have alternate window managers. I don't
intend to use kde4.*
 
Old 08-29-2009, 02:14 AM   #748
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,442

Original Poster
Rep: Reputation: 70
Quote:
Originally Posted by AGer View Post
I wrote something like the following in another thread, but now, looking at the system upgrading to JDK 6u16 and thinking if I should stay on -current or go 13.0, I guess it may be worth the effort to restate it here.

There are packages that I believe are very much out of Slackware control being developed by well respected upstream teams, like Sun JDK, Firefox, Ruby, Python, PHP, and so on. Currently the latest versions of such packages appear either in -current or on Slackbuilds. I guess it would be nice to have them in /extra of the stable branch, at least those that appear in -current anyway (that is, JDK and Firefox but not Ruby 1.9 and Python3).

My humble guess is that this may require a change to slackpkg so that it knows when to use a package from /extra and when from the main tree, while creation of the packages can be automatic and just a side effect of compiling them for -current.

It is not necessary to test such packages since if there are problems they should be considered upstream problems, not Slackware ones. Slackware does not create JDK or Firefox patches, it just packages "as is".

Currently, as far as I can see from the change logs, 12.2 has Firefox 3.0.13 while -current has firefox 3.5.2; 12.2 has JDK 6u11 while -current has JDK 6u16. In plain user words, -current is current and stable is outdated.

JDK is a perfect example why this is not OK. The practice I commonly observe whenever Java is actually in use is to test existing software with each JDK release and, based on the results of the tests, upgrade or stay. That is, there is no "right" JDK version that should be included with a distribution and it is not correct to say that 6u11 is in stable since it is well tested while 6u16 is not well tested and thus is only in -current.
Firefox and JDK are easy drop-in upgrades, so there is no point in putting a newer version in /extra after a release. Just download it from -current (or use the SlackBuild) and upgradepkg.

Quote:
Originally Posted by vonbiber View Post
Hope also we'll have alternate window managers. I don't
intend to use kde4.*
They're in there
 
Old 08-29-2009, 07:12 AM   #749
AGer
Member
 
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Blog Entries: 22

Rep: Reputation: 19
Quote:
Originally Posted by shadowsnipes View Post
Firefox and JDK are easy drop-in upgrades, so there is no point in putting a newer version in /extra after a release. Just download it from -current (or use the SlackBuild) and upgradepkg.
Yes, it is not hard. There are no hard things left with Slackware and this makes the "it is not hard" argument, regardless of the issue, invalid (obsolete?). The first 3 possibly valid arguments that come to mind are "there are other things to do", "Slackware users should never desire that", and "there are unwanted side effects".

Firefox may be the easiest to handle. Currently, there are 2 options for stable - allow Firefox to upgrade itself and get it in /opt out of the slackpkg reach or repackage with slackbuild and hope that creative Firefox people did not add a change that breaks the process. Isn't getting Firefox with slackpkg easier? If upgrading to /opt is OK, why does the firefox package exist?

Exactly what I propose had been done to KDE and is being done now to the .30 kernel. The idea is to extend the procedure to whatever possible.
 
Old 09-10-2009, 12:30 PM   #750
veeall
Member
 
Registered: May 2007
Location: Estonia
Distribution: Slackware 12.1, slackware64-current
Posts: 255

Rep: Reputation: 43
slackpkg with dependency tracing?

What if future slackpkg will have kind of functionality currently offered by utility named tracepkg?

It wouldn't go against slackware principles. Wouldn't it?
(Just a thought.)
 
  


Reply

Tags
cd, live


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware future? coyctecm Slackware 12 02-01-2006 11:03 PM
Future of Slackware kratunko Slackware 30 08-12-2005 01:31 PM
Slackware features? rusty_slacker Slackware 49 12-02-2004 05:45 AM
what are the features of the new slackware 9? ethanchic Slackware 2 09-27-2002 07:15 PM


All times are GMT -5. The time now is 06:47 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration