<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposed Feature:Backports_update_applet
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3C4FD3BBC1.5050903%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016330.html">
<LINK REL="Next" HREF="016412.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposed Feature:Backports_update_applet</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposed%20Feature%3ABackports_update_applet&In-Reply-To=%3C4FD3BBC1.5050903%40linux.it%3E"
TITLE="[Mageia-dev] Proposed Feature:Backports_update_applet">anaselli at linux.it
</A><BR>
<I>Sat Jun 9 23:10:25 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016330.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI>Next message: <A HREF="016412.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16331">[ date ]</a>
<a href="thread.html#16331">[ thread ]</a>
<a href="subject.html#16331">[ subject ]</a>
<a href="author.html#16331">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 09/06/2012 22:53, andre999 ha scritto:
><i> - Just marking all backport repos as update repos is almost enough
</I>><i> to solve the problem, in terms of the tools installing the
</I>><i> backports. Great idea ! We just have to tweak the tools so that a
</I>><i> backport is only installed as an update of a backport.
</I>e.g. as update repository.
great, at least someone got my point, i think i have said that in the
beginning of this thread or the related one for mgaupdate...
><i> - using "bp" in the file name is nice and short, and definitively
</I>><i> marks it as a backport for the tools, and for the user once
</I>><i> installed. (I would put it in the revision field.) I like this
</I>><i> approach, as it doesn't matter from where the package is installed;
</I>><i> it will always be recognized as a backport.
</I>I'm not a rpm macro guru, but i think we should change mkrel for that
and we should also manage bpmga1, bpmga2, etc. So I can't see why, since
a bpmgaX package could always be uploaded without respecting any
upgradable rules...
-----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/Tu74ACgkQqEs9DA4DquCBkACbBkHUqbBw9LK+VZeodz8FXDXl
+PQAn3hPA4DNcnaFiTDIVNAnCRuvL79E
=yhli
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016330.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI>Next message: <A HREF="016412.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16331">[ date ]</a>
<a href="thread.html#16331">[ thread ]</a>
<a href="subject.html#16331">[ subject ]</a>
<a href="author.html#16331">[ 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>