Spec URL: http://labs.linuxnetz.de/bugzilla/purple-whatsapp.spec SRPM URL: http://labs.linuxnetz.de/bugzilla/purple-whatsapp-0.4-1.20140413git.src.rpm Description: This is a WhatsApp plugin for Pidgin and libpurple messengers. It connects to the WhatsApp servers using the password (which needs to be retrieved separately). Only one client can connect at a time (including your phone). Fedora Account System Username: robert
You don't need a buildroot definition, a clean section and the initial rm in the install section. Neither do you need defattr. Why are you calling the package purple-whatsapp when the tarball is called whatsapp-purple? The version constraint for libpurple is not necessary, as it is fulfilled in any version of Fedora. The author should provide a license file to include.
(In reply to Volker Fröhlich from comment #1) > You don't need a buildroot definition, a clean section and the initial rm in > the install section. Neither do you need defattr. Because of Fedora EPEL 5. > Why are you calling the package purple-whatsapp when the tarball is called > whatsapp-purple? Because all other packages in Fedora seem to be named purple-<ext> independent of the upstream tarball name. > The version constraint for libpurple is not necessary, as it is fulfilled in > any version of Fedora. That is right, but it doesn't hurt as well IMHO. > The author should provide a license file to include. Good point, inform upstream about that.
> Because of Fedora EPEL 5. Ah, OK, I didn't expect that. The defattr is not necessary there though.
Just a side note about the Source0, you may want to check out http://fedoraproject.org/wiki/Packaging:SourceURL. If the source is via github (which it appears to be) there are some additional %global.
As per https://github.com/davidgfnet/whatsapp-purple the software is no longer maintained.