Some third party RPMs built for other distributions will work, but for best results, you should look for the source RPM (xxx.SRPM or xxx.src.rpm). Follow these steps to create a binary rpm that is specific to your versions of system libraries:
1) Install the Java Desktop System development libraries from your distribution media.
2) Now build a new binary rpm using your system libraries with the following command:
rpm --rebuild whatever.src.rpm
This will create a binary rpm in a location specific to your machine's architecture. For example:
/usr/src/packages/RPMS/i586
You can install this newly created binary rpm with:
rpm -i /usr/src/packages/RPMS/i586/whatever.rpm
> Sun Java Desktop System is based on SuSE 8.2
> therefore any SuSE rpm's should install without
> problems.
I tried to install Suse 8.2 RPMs for rcs, and found that I needed glibc 2.3.2.
JDS is operating on glibc 2.2.5.
When I upgraded to 2.3.2, the system became unstable and I had to re-install. I would like to be able to access binary RPMs compiled for JDS.
It is not feasible for me to download, say, the source for Mozilla in order to be able to install Mozilla 1.6.
Bugs in the forum software running on JDS -
Sorry to report this here, but I find that I can post a reply,
but cannot post a new message.
The new message screen just sits and looks at me when I press Post.
Note also that this Message input area I am now using is also bug-ridden.
I cannot scroll the curosr across my input text unless I keep the line length (not counting the soft breaks) short.
Great advertisemen for the product.
I am running JDS release 1.0 (Mercury) which I believe is primarily based on SuSE 8.1 (our distribution has a 2.4.24 kernel).
When I run the command "rpm --rebuild rcs-5.7-659.src.rpm" it seems to complete sucessfully.
If I do a
"man rcs" it displays the man page as expected
"rcs" it prints the usage as expected
"rpm -qa | grep -i rcs" nothing returned?
Can anyone explain this?
Also what comand can I use to see what binaries are distributed/available with a particular RPM?
It sounds like the build didn't complete. Try the --vv (verbose debugging) option. Some spec files or install scripts might look in /etc/SuSE-release and fail to install properly if they don't see the version they expect.
To list the binaries within an rpm:
rpm -qpl {yourrpm.rpm}