<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Backports Summary
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEB0857.4070302%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016961.html">
<LINK REL="Next" HREF="016858.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports Summary</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEB0857.4070302%40linux.it%3E"
TITLE="[Mageia-dev] Backports Summary">anaselli at linux.it
</A><BR>
<I>Wed Jun 27 15:19:19 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016961.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016858.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16916">[ date ]</a>
<a href="thread.html#16916">[ thread ]</a>
<a href="subject.html#16916">[ subject ]</a>
<a href="author.html#16916">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 27/06/2012 12:46, Thomas Backlund ha scritto:
>><i> I would favour tagging backports as update repos, so that in the
</I>>><i> event of a newer backport for security or bug fixes, that it will
</I>>><i> be automatically presented with other updates.
</I>><i>
</I>><i> No. as the update applet currently works it would show the backport
</I>><i> as an update even if you dont have an earlier backport installed,
</I>><i> defeating the purpose of having separate /updates vs /backports
</I>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
|<i> Enable | Update |Type |
</I>|<i> X | |Backport |
</I>or
|<i> Enable | Update |Type |
</I>|<i> X | X |Backport |
</I>
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 - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAk/rCFcACgkQqEs9DA4DquBHuACgn5YzqworNBED2KzOJBt5MDrm
T7YAn1bRhX29i1d9CwXCbi3RaU1Vuzzt
=0qjS
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016961.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016858.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16916">[ date ]</a>
<a href="thread.html#16916">[ thread ]</a>
<a href="subject.html#16916">[ subject ]</a>
<a href="author.html#16916">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>