-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 27/06/2012 12:46, Thomas Backlund ha scritto: >> I would favour tagging backports as update repos, so that in the >> event of a newer backport for security or bug fixes, that it will >> be automatically presented with other updates. > > No. as the update applet currently works it would show the backport > as an update even if you dont have an earlier backport installed, > defeating the purpose of having separate /updates vs /backports hmm, only if it is enabled as update by default. Again, let the user decide, he knows if he wants all the backports (and updated) or just cherry-peeked
| Enable | Update |Type | | X | |Backport | or | Enable | Update |Type | | X | X |Backport | Usually "Update" is blocked, but once it was clickable by User I know we can change it by editing configuration files, I propose to let the user enable again it at least for backports... Angelo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/rCFcACgkQqEs9DA4DquBHuACgn5YzqworNBED2KzOJBt5MDrm T7YAn1bRhX29i1d9CwXCbi3RaU1Vuzzt =0qjS -----END PGP SIGNATURE-----