Trying to package skype 4 but having errors...

[naoliveira]

Hi guys,

 I am trying to package skype 4 but I am getting this error:

/home/nuno/src/tmp/rpm-tmp.19nDEY: line 45: ./configure: No such file or directory

Where can I found the .configure file?

Another error was when I tried to unpack a rpm file from a fedora or opensuse distro, I received a few dependencies errors, but I have all dependencies installed, maybe is something about distros differences?

Could you help me with this 2 errors?

Regards,
Nuno.

[TerryN]

I am trying to package skype 4 but I am getting this error:

/home/nuno/src/tmp/rpm-tmp.19nDEY: line 45: ./configure: No such file or directory

It looks like you are trying to use a "generic build procedure" (configure/make/make install) which is for building packages which are supplied as source code (usually C/C++).
As far as I am aware Skype is proprietary software available only as a pre-compiled binary (no source code supplied).  The generic build procedure will not work for that type of package.  There is no configure script.

Another error was when I tried to unpack a rpm file from a fedora or opensuse distro, I received a few dependencies errors, but I have all dependencies installed, maybe is something about distros differences?

If you are receiving dependency errors then you don't have the correct dependencies installed  
To answer fully we would need to know the exact error you are receiving.
In general an alien RPM which has dependencies will fail to install usually because it's native distro may have different naming conventions, different versions of shared libraries or even use a different version of RPM.

Terry.

[Archie]

In addition, pull the Skype SRPM from any of our mirrors and take a look at the specfile.

[Agent Smith]

Hi folks,
Yesterday I packaged Skype 4.0.0.7 for PCLinuxOS.
It's in the DropBox /pack folder.
I just used the spec from the current package, and it worked smoothly.

Best regards,

A.Smith

[naoliveira]

As far as I am aware Skype is proprietary software available only as a pre-compiled binary (no source code supplied).  

That's why it failed . I thought that the files were the source code.

In general an alien RPM which has dependencies will fail to install usually because it's native distro may have different naming conventions, different versions of shared libraries or even use a different version of RPM.

I made a mistake, in RPM manual refers to SRPM and I thought it was only RPM.

In addition, pull the Skype SRPM from any of our mirrors and take a look at the specfile.

Thanks for advice, I found a SRPM from MIB. But as I am learning how to package, which way is better, use a SRPM from PcLinuxOs or from other distro and then convert?

[TerryN]

Thanks for advice, I found a SRPM from MIB. But as I am learning how to package, which way is better, use a SRPM from PcLinuxOs or from other distro and then convert?

It is ALWAYS better to start with an SRPM for PCLinuxOS if one exists.

If there isn't one for PCLinuxOS then Mageia or Mandriva SRPMS are the next best as they use similar guidelines to us but do bear in mind that they WILL need modification for use on PCLinuxOS.

Your question suggests you haven't read this
It is a good idea to read all the Sticky threads of this board  
(Some of the links may be out-of-date but a lot of questions are answered there)

Terry.

[Archie]

Thanks for advice, I found a SRPM from MIB. But as I am learning how to package, which way is better, use a SRPM from PcLinuxOs or from other distro and then convert?

It is ALWAYS better to start with an SRPM for PCLinuxOS if one exists.

Terry.

+1 on TerryN

When we update, we usually use our SRPM. If the update fails to build, there are many ways to determine why it didn't build. You can either check the hundreds of lines on the stdout (don't be scared ... you can learn to skim only for the important bits) or refer to another distro's specfile. If that is to be the case, I would go in the order of Mandriva, Suse, Fedora ...

[naoliveira]

Ok guys, but using others distro SRPM we have to make some "adjustments"  for the SRPM works in pclinuxos, and in that way we are learning a bit more, off course after we have more experience the better way is using the pclinuxos SRPM.

Anyway, after I resolved the error dependency with MIB SRPM I already have skype 4 working on my pclinuxos , thanks guys for your help, I just will move on to other package .

[Neal ManBear]

naoliveira,
Very last option to use in solving a build error is to look at spec files used by other distros. I have never had to resort to that.     

If you want to package for PCLinuxOS, first learn how PCLinuxOS packages are built. Learning how other distros do it will handicap you.     

[naoliveira]

If you want to package for PCLinuxOS, first learn how PCLinuxOS packages are built. Learning how other distros do it will handicap you.     

Maybe I didn't explain in the right way, if I have to convert from other distros to PCLinuxOS I am learning how PCLinuxOS are built, if I just get a PCLinuxOS SRPM all the work are done and there's nothing to learn with, or it isn't like this?

[Archie]

I have a feeling this is going to be a long thread ...

There has been an effort to standardize building RPMS, notably by Fedora, OpenSUSE, etc. It's understandable and beneficial that other distro's RPMS could be used in any distro. THIS IS NOT THE CASE for PCLinuxOS. Why? Simple answer, we are a small team and we do not have the manpower to adapt (make changes) to the standardization. So we stick to our own.

There are commands that other distros use to build their RPMS that we don't use in PCLinuxOS. There are dependencies used by other distros that we won't find in our repository.

There are very obvious differences, and these are what you needed to learn. But you won't be able to if you base your "learning to package for PCLinuxOS" from the ways other distros do it.

I really hope that makes sense.

[Neal ManBear]

You can learn PCLinuxOS standards by studying PCLinuxOS spec files. You can not learn our standards by studying spec files done by other distros.     

The differences between them and us can and will cause problems. They may install a package in a different directory to what we use. If you use their spec to package an update and send it to the other directory, then packages that depend on that package will error out with the message that that dependency is unavailable. Essentially it won't be, as it will be installed in the wrong place.     

Re: "Universal Standards"     
I see no reason to switch to fedora's "universal" standard.     
I see no reason to switch to suse's "universal" standard.     
I see no reason to switch to anyone's "universal" standard.     

PCLinuxOS standards work fine for PCLinuxOS.     

[naoliveira]

There are very obvious differences, and these are what you needed to learn. But you won't be able to if you base your "learning to package for PCLinuxOS" from the ways other distros do it.

You can learn PCLinuxOS standards by studying PCLinuxOS spec files. You can not learn our standards by studying spec files done by other distros.

But why are you focus on "other distro's specs" instead of "converting to pclinuxos format"? In my opinion converting to pclinuxos format it is a way to learn how this format works, and maybe is better, because we have to change something, than just look at some spec file already formatted.

The differences between them and us can and will cause problems. They may install a package in a different directory to what we use. If you use their spec to package an update and send it to the other directory, then packages that depend on that package will error out with the message that that dependency is unavailable. Essentially it won't be, as it will be installed in the wrong place.     

And this was exactly what happened when I converted skype4 spec's file from MIB to PCLinuxOS format, there were a difference in a library name, just change this name to PCLinuxOS name and now it is working.
That's why I say this is a good way to learn how PCLinuxOS specs's files works.

[Neal ManBear]

naoliveira,
Despite your insistence on it, studying spec files from other distros is not how to learn to package for PCLinuxOS.     

[naoliveira]

naoliveira,
Despite your insistence on it, studying spec files from other distros is not how to learn to package for PCLinuxOS.     

And I don't understand why you continue focus on "other distros specs" instead of "converting to pclinuxos format".
I gave you the skype 4 example, the dependency problem that I had I resolved it looking in PCLinuxOS spec's format, not in Mandriva spec's format.
I never intended to studied "others distros specs", I just tried to grab a "other distro specs" and converting to PCLinuxOS format, and I did with skype 4, maybe is not 100% but it is working. If you think this is a bad idea, you should explain why converting shouldn't be used instead of saying that studied "other distros specs" are wrong.
In the RPM manual the 1st option to make a PCLinusOS spec file is to grab a already created one from other distro and convert it.