max bianco wrote: > How do you define poorly built? I don't know much about rpm's beyond > how to install and uninstall them. Can someone tell me what makes for > a poorly built rpm? Well, one example might be a package that leaves crap around after you remove it. This might happen if the package creates files or directories in it's %post install section and doesn't remove them in the %postun section. One of the issues that the VMware rpm has had for ages is that it screws up the SELinux context on /etc/services. I've not looked closely at the the VMware packages in a while, so I don't know what other issues they might have. Making rpm packages is easy. Making goo rpm packages is a little bit more difficult, as there are many little details that can trip you up. This is why Fedora has such extensive packaging guidelines¹ and requires all packages to be submitted for a review before they can enter the distribution. ¹ http://fedoraproject.org/wiki/Packaging/Guidelines -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The sunshine bores the daylights out of me. Chasing shadows moonlight mystery.
Attachment:
pgppoFULONrBV.pgp
Description: PGP signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
