[SOLVED] About compatibility of software older than the OS.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
About compatibility of software older than the OS.
Kernel 2.6.21.5, Slackware 12.0
Hi:
Cdrdao 1.2.1 has a bug whereby it issues "ERROR: [...] START XX:XX:XX behind or at track end" when using the PREGAP sentence in certain well formed TOC files. 1.2.1 was the version which came with my slack 12.0. In http://sourceforge.net/projects/cdrdao/ they have versions (source packages) from 1.1.7 up to 1.2.3. The first version with the problem was, according to certain bug report, 1.2.0. I have two options: try one of the versions before 1.2.0 or one of the latest.
The question is this: is a version older than the one that came with my O.S. guarantied to be compatible with it?
I would just try it. If there are difficulties you can easily re-install the Slackware package. I would try it with a newer version first, may be the bug is fixed in them and the step 1.2.1 to 1.2.3 shouldn't normally cause incompatibilities. Best bet would be to read the change-logs first.
Only that when installing (installpkg) some files may get overwritten.
Of course they will, that is one of the points why proper packaging is recommended for installing software. If it does not work you can cleanly remove it try a different version.
What I meant is that, first I must removepkg and this is when some files used by other packages may be deleted. 'removepkg -warn' lists all of the files that will be removed but, as I do not know which of them are shared by other packages, the -warn option never has been of much use for me.
Nevertheless, in this case, I can see all the files that would be removed belong only to cdrdao.
The thing is that cdrdao is not in slackbuilds at present. Never mind: I have just compiled 1.2.3 and it works fine. The only drawback is that the driver does not like the drive. This I remedy using the option --driver generic-mmc-raw.
I've seen that cdrecord can use cue-sheets. It would be intersting to know if what cdrdao does can be done with it. That is, work with TOC files.
umm.. i didn't mean slackbuilds.org.
what i meant was the official slackbuilds from ftp.slackware.com/pub/slackware/slackware-xx.xx/source/ap/cdrdao
from there you can grab the source and the script that was used to build the official package
i've checked from the latest one to slackware-10.0 with cdrdao as old as 1.1.9 and probably you can find even the more older ones as well
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.