I am not sure but I don't think the importance of your little exercise with the Debian download for VariCAD viewer hit home, nobody has made any comment on your suggestion. I would like to pursue this a bit further, it seems to work.
I was using VariCAD successfully in pclos2009 then had a break from Linux work and come back well after the pclos2010 released. After some time on Forum I realised that I might not be able to install VariCAD rpm and run it in pclos2010.
rpmlib(PayloadIsLzma) <= 4.4.6-1 is needed by VariCAD_View_2010-en-2.06-1.i586
After seeing a few lines of above I was not really surprised when I downloaded the latest *.rpm from VariCAD last night that I also received that message. My luck was that I had come across this topic and noticed your effort. From your exercise I was guessing that there is nothing wrong with the *.rpm code just a compression format lzma (which I have no clue about how it is used). I have little understanding of the inner workings of running binary files etc but from your exercise I guessed you had figured out that the debian code could be unravelled from the packing and just placed in the 'proper' position and then find the 'start' file.
Well I downloaded the VariCAD.deb file: varicad2010-en_2.08_i386.deb
and followed your instructions carefully. I can confirm that VariCAD 2010 v 2.08 indeed will run very nicely under pclos2010 KDE.4.4.5 I have only had a few minutes and realised that I have forgotten quite a bit of how to run it to check the finer points.
I have found one thing I don't quite understand and may go back to VariCAD and ask for help as I have lost my initial notes of a year or two ago during my loss of a master backup partition. I can not check what I did in similar situation then. What is happening to me is that I am getting a message that only root can insert licence key.
No problem I start VariCAD with root priviliges, actually I start "varicad" via Super User Konqueror insert my licence details and I am away. I was hoping that once the licence key was accepted then I could go back to normal user and still start up VariCAD but not so, I get to the licence key window and when pressing OK I am again told only root can install.
If the worst come to pass I can run as root but it just does not seem such a good idea with me so inquisitive, any key that should not be pressed I wonder what happens if ....
For the time being I am just assuming the problem may have something to do with the unorthodox way VariCAD was installed in pclos2010. I am/was aware that this is not recommended to run outside Synaptic but while VariCAD is not AutoCAD it is very impressive for mechanical engineering 3D and I have come to like working on models. To stay in Linux I wanted a native program and it does the job for me.Stupidspencer
I have posted here to show you that it seems that pclos2010 can indeed run VariCAD and if you have not already got it working there is hope. Of course if you have found another way of getting it running I for one would be very interested to hear as there a items like desktop icons that does not get installed this way, however this is by peering into the directories that was undolded from the debian file. General
Just before finishing the post I got intrigued by the ldd
command, I only have a hazy idea what it does as ldd --help did not really enlighten me, seems to be a bit heavy going for me. I decided to navigate to where the 'start file' for VariCAD is located and then run this:
[root@localhost bin]# ldd varicad
linux-gate.so.1 => (0xffffe000)
libpthread.so.0 => /lib/i686/libpthread.so.0 (0xb77d3000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb76dd000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb76d8000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb7693000)
librt.so.1 => /lib/i686/librt.so.1 (0xb7688000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7265000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb725c000)
libXft.so.2 => /usr/lib/libXft.so.2 (0xb7248000)
libXmu.so.6 => /usr/lib/libXmu.so.6 (0xb7230000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xb7228000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xb720e000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb7204000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb71fa000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb71f2000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb71ed000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb71ea000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb71d9000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb70a8000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7029000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb6ff6000)
libm.so.6 => /lib/i686/libm.so.6 (0xb6fce000)
libGL.so.1 => /usr/lib/nvidia-current/libGL.so.1 (0xb6f0a000)
libGLU.so.1 => /usr/lib/libGLU.so.1 (0xb6e9a000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6dac000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6d8f000)
libc.so.6 => /lib/i686/libc.so.6 (0xb6c2e000)
libz.so.1 => /usr/lib/libz.so.1 (0xb6c1b000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb6bd9000)
libdl.so.2 => /lib/libdl.so.2 (0xb6bd3000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb6b31000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb6b17000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb6b0b000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb6b08000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb6b04000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb6ae7000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb6a65000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb69f5000)
libdirectfb-1.4.so.0 => /usr/lib/libdirectfb-1.4.so.0 (0xb6967000)
libfusion-1.4.so.0 => /usr/lib/libfusion-1.4.so.0 (0xb695c000)
libdirect-1.4.so.0 => /usr/lib/libdirect-1.4.so.0 (0xb6946000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb6929000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb6926000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6920000)
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xb6871000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb685a000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb6831000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb67ea000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb66ab000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb66a7000)
libXt.so.6 => /usr/lib/libXt.so.6 (0xb664c000)
libGLcore.so.1 => /usr/lib/nvidia-current/libGLcore.so.1 (0xb503b000)
libnvidia-tls.so.1 => /usr/lib/nvidia-current/tls/libnvidia-tls.so.1 (0xb5039000)
Errrrhhh what does all this mean
1.. Is there anybody understanding the finer points here, that can explain a bit about how big an obstacle this quoted line with lzma is?
2.. Is it something that affects the code or is it just a wrapping obstacle in rpm?
3.. How close is this to walking plank running this particular Debian package?
4.. Is this a problem created by VariCAD and a matter of asking for differently packed rpm