Installing without Synaptic ( an RPM file )

[PcLOSHead]

I looked around, I've seen the suggestions on that, we shouldn't go outside the repositories but this particular program I want to install, eh, I think is harmless, just an interesting program i like.

The program is Wakoopa ( It's a tracker ) 

I followed the instructions on logging in as root, typing the code
rpm -ivh /home/fahrije/Desktop/wakoopa-2.0-2.i386.rpm

but this is what follows:

Failed Dependencies:
libcurl.so.4(CURL_OPENSSL_3) is needed 


I looked for a bit and came across this, with some links shows PCLinuxOS

http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/libcurl.so.4

Any of them good to get? 

[muungwana]

opening up synaptic and then search and install a package called "libcurl4". It should give that library. You should always start with synaptic before going out to look for dependencies some place else

[PcLOSHead]

lol of course I searched for it in Synaptic first , it even shows that I have that one installed.

I just re-installed it to make sure and re-typed the code into the terminal, same message came up 

[muungwana]

my limited understanding of spec files tells me the error is then due to a failed dependency not from missing libraries on your system but from missing package name in the package database.

Installing that library will not make the error go away since it needs a specific package name(CURL_OPENSSL_3). This is one of the problem of installing packages from different distros. Different distros name the same packages differently and different packages may fail to install because they are looking for package names that are different.

Why not make a package request for this program and wait for it to find its way to the repository and install it from there.

where did you get this package from?

[ElCuervo]

Installing anything from outside the repository will eventually make you regret it, and certainly will leave you with a non-standard installation that will make getting help here impossible. The correct path is to make a package request.

[PcLOSHead]

Thanks to the both of you for the replies.

I got the file from the site itself.

http://social.wakoopa.com/account/download#

That's interesting though that they will name rpm's or package them as one size fits all meanwhile diff distros package differently.

Damn Commi's assuming everything is the same 

lol. I didn't make a request since I didn't know I had to, thought I could get it working without going that far.

But if you guys suggest for me to do so then I will...I'll wait first for your replies to this

[muungwana]

that link requires a user to be logged in, meaning some sort of registration is required.

If you have an account, you can check to see if they allow their package to be redistributed, they must allow this for it to be included in the repository.

Its usually a good idea to request for packages first and then install them from the repository because that will mean they are checked and are known to work with pclinuxos and they will became available to the whole pclinuxos community.

Since you already have libcurl.so4 installed, you can install the package without checking for dependencies with this command

rpm -ivh --nodeps  /home/fahrije/Desktop/wakoopa-2.0-2.i386.rpm

You should know that you are installing a package ignoring a dependency and this may work now but may cause serious problems down the line and the problem will be difficult to trouble shoot and support will probably not be provided. This is a very serious thing you are doing. I can not stress this point enough. Continue at your own risk and have an installation disk close by, you may need it

[YouCanToo]

I looked around, I've seen the suggestions on that, we shouldn't go outside the repositories but this particular program I want to install, eh, I think is harmless, just an interesting program i like.

The program is Wakoopa ( It's a tracker ) 

I followed the instructions on logging in as root, typing the code
rpm -ivh /home/fahrije/Desktop/wakoopa-2.0-2.i386.rpm

but this is what follows:

Failed Dependencies:
libcurl.so.4(CURL_OPENSSL_3) is needed 


I looked for a bit and came across this, with some links shows PCLinuxOS

http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/libcurl.so.4

Any of them good to get? 

So you went ahead and tried it anyway     There is a reason why it is suggested that you not install from outside the repository!

[PcLOSHead]

[quote
So you went ahead and tried it anyway     There is a reason why it is suggested that you not install from outside the repository!
[/quote]

 :oNo!

lol, I mailed the devs to ask them if it can be repackaged as was suggested and I will submit a request in the forums ( i just feel awkward asking since I brought it up, it has to be a lot of work i think right? )

Eh, better to try than not to I guess. But no, again, I'm not risking before finding a "correct" way first 

[Archie]

PcLOSHead, it is obvious that you are a new Linux user. If you value your install and want it to work well, you need to understand that not all RPMS can work for all RPM-based distros. There's a lot more work done to get these apps to work for PCLinuxOS. If this app you want to install is Open Source and GPL, you can make a request on the Package Suggest of this forum (read that section's rules).

But do not try your experiments on a working install, unless you want to risk borking your system. There are tools you can use to try this experiments out. VirtualBox is one such environment.

[PcLOSHead]

I'm a new user to rpm distros, been more on the Debian circuit thus far so when I'd see a file of theirs, it would usually work, hence my naiveness to rpms being equal.

But I understand you and the rpm creation. I did post to the request but Tex just told me that it's a coding that isn't going to work well so it won't be worked on.

 

[Texstar]

I'm a new user to rpm distros, been more on the Debian circuit thus far so when I'd see a file of theirs, it would usually work, hence my naiveness to rpms being equal.

But I understand you and the rpm creation. I did post to the request but Tex just told me that it's a coding that isn't going to work well so it won't be worked on.

 

I'm afraid there is simply nothing to work on. There is no source code or a source rpm that contains source code. The link you posted is the result of a rpm build against whatever libraries they had installed on their system at the time of the build. We don't know what libraries or versions of libraries the rpm is linked against but it doesn't match what we have in our repository.

When I build an rpm it is built against the most current stable/secure libraries in the PCLinuxOS repository which may be different versions than other distributions. The end result is the program is linked against those libraries. This is why each distribution has their own software repository.

Tex

[PcLOSHead]

I'm a new user to rpm distros, been more on the Debian circuit thus far so when I'd see a file of theirs, it would usually work, hence my naiveness to rpms being equal.

But I understand you and the rpm creation. I did post to the request but Tex just told me that it's a coding that isn't going to work well so it won't be worked on.

 

I'm afraid there is simply nothing to work on. There is no source code or a source rpm that contains source code. The link you posted is the result of a rpm build against whatever libraries they had installed on their system at the time of the build. We don't know what libraries or versions of libraries the rpm is linked against but it doesn't match what we have in our repository.

When I build an rpm it is built against the most current stable/secure libraries in the PCLinuxOS repository which may be different versions than other distributions. The end result is the program is linked against those libraries. This is why each distribution has their own software repository.

Tex

Well said, thank you very much for clearing up the rpm confusion with me 

[muungwana]

[ink@mtz New]$ rpm2cpio wakoopa-2.0-2.i386.rpm  | cpio -idmv
.
./usr
./usr/bin
./usr/bin/wakoopa
./usr/share
./usr/share/applications
./usr/share/applications/wakoopa.desktop
./usr/share/doc
./usr/share/doc/wakoopa
./usr/share/doc/wakoopa/changelog.gz
./usr/share/pixmaps
./usr/share/pixmaps/wakoopa.png
./usr/share/wakoopa
./usr/share/wakoopa/pixmaps
./usr/share/wakoopa/pixmaps/hicolor
./usr/share/wakoopa/pixmaps/hicolor/16x16
./usr/share/wakoopa/pixmaps/hicolor/16x16/status
./usr/share/wakoopa/pixmaps/hicolor/16x16/status/wakoopa.png
./usr/share/wakoopa/pixmaps/hicolor/16x16/status/wakoopa_alert.png
./usr/share/wakoopa/pixmaps/hicolor/16x16/status/wakoopa_error.png
./usr/share/wakoopa/pixmaps/hicolor/16x16/status/wakoopa_paused.png
./usr/share/wakoopa/pixmaps/logo_homepage.png
./usr/share/wakoopa/pixmaps/wakoopa.png
./usr/share/wakoopa/pixmaps/wakoopa_large.png
./usr/share/wakoopa/pixmaps/wakoopa_menu_alert.png
1704 blocks

The above output is all the files in the package, i think you can install this package without worrying if it will do damage to your computer. It only contains one executable with a name that is unlikely to collide with any other executable name and the rest are supporting files and they dont look like they will interfere with any other file provided by the distro.

I tried to run it and it started fine here, i just run it from the extracted files above, i did not install it.

If you want to install it, use the command i gave in on of my posts above.

[PcLOSHead]

I beat you to it Muungwana 

lol but thanks for testing it to reveal more, I appreciate it