-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello:
I was reading a blog posted to Planet Fedora[0], and found the following
paragraph:
"I did notice one quirk they kind of bugged me, while this is not a bug, and
it is in fact an intentional change, I don’t understand the methodology behind
the change. I’m talking about the fact that if you ever create your own RPMs
and Fedora things have become slightly more confusing. It used to be that all
you needed to do in order to sign and build RPM packages was to install the
development tools group from Yum. It seems for whatever reason they’ve taken
the GPG signing integration out of RPM by default. This functionality can of
course be added back, but it requires installing a separate package. There’s
absolutely no documentation that I’ve been able to find that explains the
reasoning behind this change, or even that the change took place. I literally
spent three hours trying to sign a package through RPM only to find that some
person on a forum somewhere discovered that this RPM signing functionality was
moved into a separate package called rpm-sign."
Should this change be documented in the release notes? Should it be added now?
Christopher.
[0]
http://www.andyjamison.com/andy/2011/06/23/final-thoughts-on-ubuntu-11-04-
and-
fedora-15/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+AndrewTheHopelessTechieLinux+%28Andrew+the+Hopeless+Techie+%C2%BB+Linux%29
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQEcBAEBAgAGBQJOBULoAAoJEInCktGVqZ8V038H/041hv6gLHPhUfuh/T90vIi9
FOXFOLrLnvB6t2dfPG6tszyID7yzRdwwS8Xvs+peoNcN7bsxO8cuU9NDdHxeRmfI
WaN7bC8ybhnXf50gG9V7a17R2cQn0f5Vcx2QIzf2J/3ig+blp1nPo2admGoqoXmL
gWz81SHKy7zakzGNtsENz/onUb4hWtVZU3AbaTtjZYcERjPr0J99gE3iKIYRu4jy
9qMMMMDJgwheJuvU1oLoRtW58xrQo8JT5l4XJN/Q9p79+l4G2Eyogn1iuqjkqR6j
DJUQ7/5298wjAoMqNcgVLROO1itW3yvjzRv7k3r+YJTzzfC/S2G0Ht4nuS7Vb9M=
=4nPY
-----END PGP SIGNATURE-----