diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20101008 | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20101008')
34 files changed, 3689 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101008/001020.html b/zarb-ml/mageia-dev/20101008/001020.html new file mode 100644 index 000000000..455243a07 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001020.html @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Talk of Browsers + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Talk%20of%20Browsers&In-Reply-To=%3C201010080029.57696.r.h.michel%2Bmageia%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="001021.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Talk of Browsers</H1> + <B>Renaud MICHEL</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Talk%20of%20Browsers&In-Reply-To=%3C201010080029.57696.r.h.michel%2Bmageia%40gmail.com%3E" + TITLE="[Mageia-dev] Talk of Browsers">r.h.michel+mageia at gmail.com + </A><BR> + <I>Fri Oct 8 00:29:57 CEST 2010</I> + <P><UL> + + <LI>Next message: <A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1020">[ date ]</a> + <a href="thread.html#1020">[ thread ]</a> + <a href="subject.html#1020">[ subject ]</a> + <a href="author.html#1020">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On jeudi 07 octobre 2010 at 23:39, Sorteal wrote : +><i> Why are we even talking about removing Konqueror?? So many people use +</I>><i> it as their default file manager and ftp client that removing it seems +</I>><i> crazy. While I do agree that Konqueror is not the greatest web browser +</I>><i> around and Rekonq is a much better choice for a pure Qt/KDE browser, I +</I>><i> do not think we should be excluding Konqueror at all. +</I> +I don't think anybody suggested to remove konqueror, but rather to provide +firefox as the default browser on a new install. +Although I prefer konqueror, I think it is reasonable as most people expect +to have firefox (and I use it for the few sites that I visit and render +badly in konqueror (actually, it is more about javascript than rendering)). + +><i> Plus, Dolphin still requires certain parts of Konqueror to function +</I>><i> correctly if I'm not mistaken. +</I> +Right, but those parts are in separate libraries which can (and will) be +installed without installing konqueror itself. + +><i> While at first I found Dolphin rather weak in comparison to Konqueror, +</I>><i> as far as file management went, it has improved over the last couple of +</I>><i> years. Now, I actually prefer Dolphin over Konqueror when it comes to +</I>><i> file management but I still use Konqueror for ftp or when I need a all +</I>><i> in one kind of tool. If Konqueror could render web pages as well as +</I>><i> Rekonq, Firefox, or Chromium I'd definitely use it as my default web +</I>><i> browser. +</I> +There is a webkit kpart which can be used instead of the standard khtml one. +In mdv2010.1 it is provided by package webkitkde. +I think I read somewhere that it was greatly improved in KDE 4.5 (or was it +during a summer of code after KDE 4.5 release?) with better KDE integration. + +-- +Renaud Michel +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1020">[ date ]</a> + <a href="thread.html#1020">[ thread ]</a> + <a href="subject.html#1020">[ subject ]</a> + <a href="author.html#1020">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001021.html b/zarb-ml/mageia-dev/20101008/001021.html new file mode 100644 index 000000000..6c135ecb0 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001021.html @@ -0,0 +1,183 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAE5C89.9040501%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001020.html"> + <LINK REL="Next" HREF="001022.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAE5C89.9040501%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 01:49:29 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001020.html">[Mageia-dev] Talk of Browsers +</A></li> + <LI>Next message: <A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1021">[ date ]</a> + <a href="thread.html#1021">[ thread ]</a> + <a href="subject.html#1021">[ subject ]</a> + <a href="author.html#1021">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Part of the recent thread about what the desirable release cycle should +be devolved into a discussion of how backports works and whether or not +it's suitable. I'd like to examine this issue. + +The current urpmi repository architecture serves purposes that were +meaningful to Mandriva. It segregates main from contrib for statement +of support reasons, it separates non-free from main for philosophical +reasons, and it separates restricted from main for legal and business +reasons. + +This works pretty well for cooker, where you either want a particular +category of package considered or you don't, but the reuse of this model +for updates, backports, and testing in released versions isn't as good a +fit. + +The root of the problem is that the user base is different. Users of +cooker want the latest and greatest of everything, and have accepted +that if something breaks in cooker, it may stay broken for awhile. +Users of released versions vary all over the map, from people who never +want anything to change to people who want some specific updates to +people who want everything new but want it stable. Users of cooker +rarely think about security updates, because in grabbing everything +available constantly, the security updates are "just there". With users +of released versions, they may have to opt-in for security updates, and +usually want to treat other updates differently. + +I'd like to propose the following model for updating released versions: + +1) Users should not have to see, except in minor ways, the different +repositories. Urpmi may see them, and advanced or ideologically polar +users may care about them (e.g. free vs non-free), but most users +won't. Instead, let urpmi or rpmdrake have knowledge about all +repositories whether enabled or not, and display the offerings with an +icon, tooltip, or extra column that indicates the status of the package. + +2) The update tool we give these users should distinguish between +security updates and backports/testing, but present them both. This is +very much like the Windows Update model, where all available fixes are +divided into "Critical System Updates" and "Software Updates". We don't +really have the same support constraints as Mandriva, and there's no +need to automatically disable backports across the board, and not even +present the backports as possibilities. + +3) Users should be able to enable options for each category +independently. Most users would probably want security updates applied +automatically, but would want to be notified of availability of +backports or testing and choose those manually. + +(Here's the biggie :-) ) +4) We need to enhance the urpmi.recover functionality and bring it fully +into mainstream urpmi so that ANY PACKAGE CAN BE ROLLED BACK TO ITS +PREVIOUS VERSION (sorry for the caps). If we don't want to be stuck +with trying to reconcile our desire to QA some packages better than +others with some users' desires to at least *try* the newest stuff, then +we need to allow them to move forwards and backwards in the package +history as easily as possible. + +Yes, I know this is problematic. It means that we have to do a really +good job of getting dependencies right. But if the dependencies *are* +right, then this should be doable. + +It means that we need to expand the logic in urpmi that can currently +identify the packages that need to be uninstalled if some other package +is uninstalled so that it can take into account the package it will be +installing in its place (and the other older versions of packages that +it will require), and compare the two lists to produce a "diff". + +It needs to decide which changes can be "quiet", e.g. "A" 1.3 requires +"B" 1.3" and "A" 1.2 requires "B" 1.2, so a request to replace "A" 1.3 +with "A" 1.2 would cause a replacement of "B" 1.3 with "B" 1.2 in the +same transaction. This may have a cascading effect. In any event, the +user should be told what's going to be backlevelled, but specifically +*not* see the current urpmi list of everything that will have to be +removed if "A" 1.3 is removed if most of that stuff is simply going to +be replaced with its own previous versions. In other words, rather than +tell the user that removing "A" 1.3 is going to remove half of KDE and +scare the sh*t out of him, just tell him that the following packages are +going to have to be backlevelled as well. If there really are things +that can't be undone and redone, that should be a separate highly +visible prompt. + +This will require some extended transactional support in urpmi, I would +think, because we'd literally have to overrule rpm about pulling stuff +out from under the feet of other packages if we knew we were going to +put it back. That would mean that we'd have the responsibility of +ensuring that the transaction either committed fully from our +perspective, or got fully rolled back. + +This also means that packagers would have to be aware of packages that +reformat their application files as the version increases, and would +have to archive previous versions using some naming scheme so that they +could be restored (and the current version archived) if an uninstall was +requested. Of course, this would require a prompt to the user to inform +him that any configuration changes made since the upgrade would be +lost. We'd probably also have to expand the "rpmnew" concept to be +version-specific. + +Yes, I realize that a couple of clicks could require a *lot* of +processing; but that can happen today, and the user would still get a +prompt about what was going to be done. + +========================= + +If all this were done, updates/backports/testing could be touted as a +"try it" environment. Click on the update(s) you want to try, we'll +tell you what else we're going to have to upgrade as well, and if for +some reason it doesn't work, you click to restore it to version x.x, we +tell you what will also be restored, and we do it. That way, we don't +have to worry about "guaranteeing" perfect quality updates. If we +missed something, and it doesn't work for you, just roll it back. + +This does require access to all previous versions of each package since +release. However, unless we screw up royally on a recurring basis, the +demand for these intermediate packages should be *much* lighter than for +the current versions, so hosting them on a Mageia primary or possibly +the first-tier mirrors should be sufficient. + +It may be that a good implementation of this would require the +availability of significant disk space for translation-related backups +or such, on the root partition or some other designated partition. If +so, we should determine if there is sufficient space, and if not, alert +the user that his choices are to abort the update or else realize that +he won't be able to roll back. Windows XP SPs do this. I don't see a +problem with this, since the current urpmi response to insufficient disk +space is basically to abort the package install but keep going. + +Thoughts ? +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001020.html">[Mageia-dev] Talk of Browsers +</A></li> + <LI>Next message: <A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1021">[ date ]</a> + <a href="thread.html#1021">[ thread ]</a> + <a href="subject.html#1021">[ subject ]</a> + <a href="author.html#1021">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001022.html b/zarb-ml/mageia-dev/20101008/001022.html new file mode 100644 index 000000000..47be1df6c --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001022.html @@ -0,0 +1,229 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8ls6o%2434h%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001021.html"> + <LINK REL="Next" HREF="001032.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8ls6o%2434h%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 03:29:59 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1022">[ date ]</a> + <a href="thread.html#1022">[ thread ]</a> + <a href="subject.html#1022">[ subject ]</a> + <a href="author.html#1022">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-07 19:49, Frank Griffin a écrit : +><i> Part of the recent thread about what the desirable release cycle should +</I>><i> be devolved into a discussion of how backports works and whether or not +</I>><i> it's suitable. I'd like to examine this issue. +</I>><i> +</I>><i> The current urpmi repository architecture serves purposes that were +</I>><i> meaningful to Mandriva. It segregates main from contrib for statement +</I>><i> of support reasons, it separates non-free from main for philosophical +</I>><i> reasons, and it separates restricted from main for legal and business +</I>><i> reasons. +</I>><i> +</I>><i> This works pretty well for cooker, where you either want a particular +</I>><i> category of package considered or you don't, but the reuse of this model +</I>><i> for updates, backports, and testing in released versions isn't as good a +</I>><i> fit. +</I>><i> +</I>><i> The root of the problem is that the user base is different. Users of +</I>><i> cooker want the latest and greatest of everything, and have accepted +</I>><i> that if something breaks in cooker, it may stay broken for awhile. +</I>><i> Users of released versions vary all over the map, from people who never +</I>><i> want anything to change to people who want some specific updates to +</I>><i> people who want everything new but want it stable. Users of cooker +</I>><i> rarely think about security updates, because in grabbing everything +</I>><i> available constantly, the security updates are "just there". With users +</I>><i> of released versions, they may have to opt-in for security updates, and +</I>><i> usually want to treat other updates differently. +</I>><i> +</I>><i> I'd like to propose the following model for updating released versions: +</I>><i> +</I>><i> 1) Users should not have to see, except in minor ways, the different +</I>><i> repositories. Urpmi may see them, and advanced or ideologically polar +</I>><i> users may care about them (e.g. free vs non-free), but most users +</I>><i> won't. Instead, let urpmi or rpmdrake have knowledge about all +</I>><i> repositories whether enabled or not, and display the offerings with an +</I>><i> icon, tooltip, or extra column that indicates the status of the package. +</I>><i> +</I>><i> 2) The update tool we give these users should distinguish between +</I>><i> security updates and backports/testing, but present them both. This is +</I>><i> very much like the Windows Update model, where all available fixes are +</I>><i> divided into "Critical System Updates" and "Software Updates". We don't +</I>><i> really have the same support constraints as Mandriva, and there's no +</I>><i> need to automatically disable backports across the board, and not even +</I>><i> present the backports as possibilities. +</I>><i> +</I>><i> 3) Users should be able to enable options for each category +</I>><i> independently. Most users would probably want security updates applied +</I>><i> automatically, but would want to be notified of availability of +</I>><i> backports or testing and choose those manually. +</I>><i> +</I>><i> (Here's the biggie :-) ) +</I>><i> 4) We need to enhance the urpmi.recover functionality and bring it fully +</I>><i> into mainstream urpmi so that ANY PACKAGE CAN BE ROLLED BACK TO ITS +</I>><i> PREVIOUS VERSION (sorry for the caps). If we don't want to be stuck +</I>><i> with trying to reconcile our desire to QA some packages better than +</I>><i> others with some users' desires to at least *try* the newest stuff, then +</I>><i> we need to allow them to move forwards and backwards in the package +</I>><i> history as easily as possible. +</I>><i> +</I>><i> Yes, I know this is problematic. It means that we have to do a really +</I>><i> good job of getting dependencies right. But if the dependencies *are* +</I>><i> right, then this should be doable. +</I>><i> +</I>><i> It means that we need to expand the logic in urpmi that can currently +</I>><i> identify the packages that need to be uninstalled if some other package +</I>><i> is uninstalled so that it can take into account the package it will be +</I>><i> installing in its place (and the other older versions of packages that +</I>><i> it will require), and compare the two lists to produce a "diff". +</I>><i> +</I>><i> It needs to decide which changes can be "quiet", e.g. "A" 1.3 requires +</I>><i> "B" 1.3" and "A" 1.2 requires "B" 1.2, so a request to replace "A" 1.3 +</I>><i> with "A" 1.2 would cause a replacement of "B" 1.3 with "B" 1.2 in the +</I>><i> same transaction. This may have a cascading effect. In any event, the +</I>><i> user should be told what's going to be backlevelled, but specifically +</I>><i> *not* see the current urpmi list of everything that will have to be +</I>><i> removed if "A" 1.3 is removed if most of that stuff is simply going to +</I>><i> be replaced with its own previous versions. In other words, rather than +</I>><i> tell the user that removing "A" 1.3 is going to remove half of KDE and +</I>><i> scare the sh*t out of him, just tell him that the following packages are +</I>><i> going to have to be backlevelled as well. If there really are things +</I>><i> that can't be undone and redone, that should be a separate highly +</I>><i> visible prompt. +</I>><i> +</I>><i> This will require some extended transactional support in urpmi, I would +</I>><i> think, because we'd literally have to overrule rpm about pulling stuff +</I>><i> out from under the feet of other packages if we knew we were going to +</I>><i> put it back. That would mean that we'd have the responsibility of +</I>><i> ensuring that the transaction either committed fully from our +</I>><i> perspective, or got fully rolled back. +</I>><i> +</I>><i> This also means that packagers would have to be aware of packages that +</I>><i> reformat their application files as the version increases, and would +</I>><i> have to archive previous versions using some naming scheme so that they +</I>><i> could be restored (and the current version archived) if an uninstall was +</I>><i> requested. Of course, this would require a prompt to the user to inform +</I>><i> him that any configuration changes made since the upgrade would be +</I>><i> lost. We'd probably also have to expand the "rpmnew" concept to be +</I>><i> version-specific. +</I>><i> +</I>><i> Yes, I realize that a couple of clicks could require a *lot* of +</I>><i> processing; but that can happen today, and the user would still get a +</I>><i> prompt about what was going to be done. +</I>><i> +</I>><i> ========================= +</I>><i> +</I>><i> If all this were done, updates/backports/testing could be touted as a +</I>><i> "try it" environment. Click on the update(s) you want to try, we'll +</I>><i> tell you what else we're going to have to upgrade as well, and if for +</I>><i> some reason it doesn't work, you click to restore it to version x.x, we +</I>><i> tell you what will also be restored, and we do it. That way, we don't +</I>><i> have to worry about "guaranteeing" perfect quality updates. If we +</I>><i> missed something, and it doesn't work for you, just roll it back. +</I>><i> +</I>><i> This does require access to all previous versions of each package since +</I>><i> release. However, unless we screw up royally on a recurring basis, the +</I>><i> demand for these intermediate packages should be *much* lighter than for +</I>><i> the current versions, so hosting them on a Mageia primary or possibly +</I>><i> the first-tier mirrors should be sufficient. +</I>><i> +</I>><i> It may be that a good implementation of this would require the +</I>><i> availability of significant disk space for translation-related backups +</I>><i> or such, on the root partition or some other designated partition. If +</I>><i> so, we should determine if there is sufficient space, and if not, alert +</I>><i> the user that his choices are to abort the update or else realize that +</I>><i> he won't be able to roll back. Windows XP SPs do this. I don't see a +</I>><i> problem with this, since the current urpmi response to insufficient disk +</I>><i> space is basically to abort the package install but keep going. +</I>><i> +</I>><i> Thoughts ? +</I>><i> +</I> +Hi FranK: + +As it seems we keep going in circles on this Romain has arranged the +following so that the threads on this topic become more focussed: + +-------------- + +It has been posted before but I guess it's a good read for anyone +willing to push an argument in this debate: +<A HREF="http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/">http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/</A> + +It is a nice post explaining the existing different point of views +(bonus to clever points about updates frequency and presentation). + +Now, in the same vein, let's put the discussion at rest a little and +have each interested person write down an article with arguments for +the why's and how's. So here is a page for that: +<A HREF="http://mageia.org/wiki/doku.php?id=rollingdebate">http://mageia.org/wiki/doku.php?id=rollingdebate</A> + +Please write down your point of view, detail it as explained on the +wiki page, link it and a week from now, everyone involved in the +discussion can have a look at it for a summary. + +That won't trigger a change decision at once (way too soon anyway, we +have to roll a first release to assess our new build system and +infrastructure and organisation) but it may at least lay down all +arguments and allow to have a better view of what everyone understand, +agree on definitions and see what is really at stake here. For later +reference, discussion and decision. + +Thanks a lot. + +Cheers, + +Romain + +-------------- + +Marc + + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1022">[ date ]</a> + <a href="thread.html#1022">[ thread ]</a> + <a href="subject.html#1022">[ subject ]</a> + <a href="author.html#1022">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001023.html b/zarb-ml/mageia-dev/20101008/001023.html new file mode 100644 index 000000000..a1a41cdb1 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001023.html @@ -0,0 +1,108 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C20101007233017.e4e545f9.gato2707%40yahoo.com.mx%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001046.html"> + <LINK REL="Next" HREF="001025.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>Fernando Parra</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C20101007233017.e4e545f9.gato2707%40yahoo.com.mx%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">gato2707 at yahoo.com.mx + </A><BR> + <I>Fri Oct 8 06:30:17 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001025.html">[Mageia-dev] test +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1023">[ date ]</a> + <a href="thread.html#1023">[ thread ]</a> + <a href="subject.html#1023">[ subject ]</a> + <a href="author.html#1023">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, 7 Oct 2010 17:43:23 +0200 +Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi-QFKgK+z4sOrR7s880joybQ at public.gmane.org</A>> wrote: + +><i> +</I>><i> Le jeudi 7 octobre 2010 17:15:45, Romain d'Alverny a écrit : +</I>><i> > So the above linked wiki page is about stating and nailing down the problem +</I>><i> > several people here seem to agree there is: +</I>><i> > - first, make sure everyone speak about the same thing; so everyone should +</I>><i> > state her own point of view, detailed; +</I>><i> > - second, work this refined problem in depth, so that we see what is really +</I>><i> > the problem, and not only the symptoms; +</I>><i> > - third, once the problem is clearly stated, the solution(s) may be more +</I>><i> > obvious to see/discute/define. +</I>><i> > +</I>><i> > Note that at this current stage of discussion, it may as well be that there are +</I>><i> > _several_ issues mixed as one. So we could as well split the problem into +</I>><i> > relevant parts. +</I>><i> > +</I>><i> +</I>><i> I think I see what you mean : you want the thing to be more globally thought that just pointing at some specifif improvements (whatever needed they may be). I'll try to stay in the frame, and will try to show that backports perception indeed has something to do with the feeling that updating your "favorite" applications is impossible or difficult in today's model :) +</I>><i> +</I>><i> Regards +</I>><i> +</I>><i> Samuel Verschelde +</I>><i> +</I>><i> +</I>Hi Everybody. + +Now I'm really happy, finally I think we are talking about the big goal: Usability and End User Satisfaction! + +I propose close this particular thread at it's present state, at now it's hard to follow each one points of view. + +I think is time to push harder, we need go to the desk and prepare a better structured documents as Marc proposed. + +A final recommendation. We must think in the End User first, and later in technical issues, there is no matter how it can be sound impossible, remember When Jules Verne wrote about a trip to the moon, everyone thought it would be impossible, and now we see that it is 40 years since man landed on the lunar surface. + +Think new, think magic, think Mageia + + <<gato27 +-- +Fernando Parra <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">gato2707 at yahoo.com.mx</A>> +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001025.html">[Mageia-dev] test +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1023">[ date ]</a> + <a href="thread.html#1023">[ thread ]</a> + <a href="subject.html#1023">[ subject ]</a> + <a href="author.html#1023">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001024.html b/zarb-ml/mageia-dev/20101008/001024.html new file mode 100644 index 000000000..96faa590a --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001024.html @@ -0,0 +1,97 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101008073609.GA10383%40maude.comedia.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001048.html"> + <LINK REL="Next" HREF="001026.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Luca Berra</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101008073609.GA10383%40maude.comedia.it%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">bluca at vodka.it + </A><BR> + <I>Fri Oct 8 09:36:09 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1024">[ date ]</a> + <a href="thread.html#1024">[ thread ]</a> + <a href="subject.html#1024">[ subject ]</a> + <a href="author.html#1024">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, Oct 07, 2010 at 07:49:29PM -0400, Frank Griffin wrote: +><i>I'd like to propose the following model for updating released versions: +</I>><i> +</I>><i>1) Users should not have to see, except in minor ways, the different +</I>><i>repositories. Urpmi may see them, and advanced or ideologically polar +</I>><i>users may care about them (e.g. free vs non-free), but most users +</I>I object to this specific point, if what we are doing is free software +that should be made clear to users. and i believe the user shold be +asked wether they want to use only free software or not. + +><i>2) The update tool we give these users should distinguish between +</I>><i>security updates and backports/testing, but present them both. This is +</I>updates are not necessarily limited to security, but ok +backports is one thing, testing is a completely different one +the only use for testing is pulling out a specific (set of) packages for +QA purpose, no user should ever see those. +but the idea of separating the two in the user interface is sound. + +><i>(Here's the biggie :-) ) +</I>><i>4) We need to enhance the urpmi.recover functionality and bring it fully +</I>><i>into mainstream urpmi so that ANY PACKAGE CAN BE ROLLED BACK TO ITS +</I>><i>PREVIOUS VERSION (sorry for the caps). If we don't want to be stuck +</I>I just read it 3 times, and i still believe doing the above might prove to be a +nightmare. +rolling back a single, well identified change is a doable task. +rolling back proceduraly a complex change becomes exponentially complex +even for experienced system engineers, let alone a piece of software. + +i'll spend more time on doing qa on packages pushed to released distros. + +L. + + +-- +Luca Berra -- <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bluca at vodka.it</A> +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1024">[ date ]</a> + <a href="thread.html#1024">[ thread ]</a> + <a href="subject.html#1024">[ subject ]</a> + <a href="author.html#1024">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001025.html b/zarb-ml/mageia-dev/20101008/001025.html new file mode 100644 index 000000000..14dff3de2 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001025.html @@ -0,0 +1,77 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] test + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20test&In-Reply-To=%3C201010081129.24097.anaselli%40linux.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001023.html"> + <LINK REL="Next" HREF="001027.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] test</H1> + <B>Angelo Naselli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20test&In-Reply-To=%3C201010081129.24097.anaselli%40linux.it%3E" + TITLE="[Mageia-dev] test">anaselli at linux.it + </A><BR> + <I>Fri Oct 8 11:29:20 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1025">[ date ]</a> + <a href="thread.html#1025">[ thread ]</a> + <a href="subject.html#1025">[ subject ]</a> + <a href="author.html#1025">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Sorry +since my provider was down i've been bounced... + +Angelo +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 198 bytes +Desc: This is a digitally signed message part. +URL: </pipermail/mageia-dev/attachments/20101008/988b1e23/attachment.asc> +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1025">[ date ]</a> + <a href="thread.html#1025">[ thread ]</a> + <a href="subject.html#1025">[ subject ]</a> + <a href="author.html#1025">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001026.html b/zarb-ml/mageia-dev/20101008/001026.html new file mode 100644 index 000000000..f112ae7ad --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001026.html @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C1286537531.1552.94.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001024.html"> + <LINK REL="Next" HREF="001033.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C1286537531.1552.94.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">misc at zarb.org + </A><BR> + <I>Fri Oct 8 13:32:11 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1026">[ date ]</a> + <a href="thread.html#1026">[ thread ]</a> + <a href="subject.html#1026">[ subject ]</a> + <a href="author.html#1026">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 08 octobre 2010 à 09:36 +0200, Luca Berra a écrit : +><i> On Thu, Oct 07, 2010 at 07:49:29PM -0400, Frank Griffin wrote: +</I>><i> > +</I>><i> >(Here's the biggie :-) ) +</I>><i> >4) We need to enhance the urpmi.recover functionality and bring it fully +</I>><i> >into mainstream urpmi so that ANY PACKAGE CAN BE ROLLED BACK TO ITS +</I>><i> >PREVIOUS VERSION (sorry for the caps). If we don't want to be stuck +</I>><i> I just read it 3 times, and i still believe doing the above might prove to be a +</I>><i> nightmare. +</I>><i> rolling back a single, well identified change is a doable task. +</I>><i> rolling back proceduraly a complex change becomes exponentially complex +</I>><i> even for experienced system engineers, let alone a piece of software. +</I> +We could, using brtfs/lvm snapshots. But this may produce some hidden +side effects. Maybe we could do the reverse : +ie, we do a clone / snapshot for testing the upgrade ( maybe in a vm, +except a vm would not help to test real hardware issue ), and if people +are not satisfied , they do not put it in "production". + +I think there was a presentation about rpm rollback at FOSDEM this year +( or last year, maybe ), but I didn't really listened, as I do not +remember how it ended. + +-- +Michael Scherer + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1026">[ date ]</a> + <a href="thread.html#1026">[ thread ]</a> + <a href="subject.html#1026">[ subject ]</a> + <a href="author.html#1026">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001027.html b/zarb-ml/mageia-dev/20101008/001027.html new file mode 100644 index 000000000..595bbe446 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001027.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] What do you think about create a Mageia Welcome Center? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%20Center%3F&In-Reply-To=%3C4CAF20BE.8070405%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001025.html"> + <LINK REL="Next" HREF="001029.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] What do you think about create a Mageia Welcome Center?</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%20Center%3F&In-Reply-To=%3C4CAF20BE.8070405%40arcor.de%3E" + TITLE="[Mageia-dev] What do you think about create a Mageia Welcome Center?">doktor5000 at arcor.de + </A><BR> + <I>Fri Oct 8 15:46:38 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001025.html">[Mageia-dev] test +</A></li> + <LI>Next message: <A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1027">[ date ]</a> + <a href="thread.html#1027">[ thread ]</a> + <a href="subject.html#1027">[ subject ]</a> + <a href="author.html#1027">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> Am 30.09.2010 12:34, schrieb Olivier Méjean: +><i> Le jeudi 30 septembre 2010 12:19:43, Robert Xu a écrit : +</I>><i> Is a survey necessary ? +</I>><i> +</I>It's not really necessary. For example, in mandriva my laptop had no internet +when booting the first time, as my wireless needs a firmware. So i never +completed the survey, and as it only started on the first boot, mandriva +never got any real data from me. Maybe when the infrastructure is up +and some releases were made, this can be discussed again. + + +What would be interesting is to count the mageia installations. Create +a GUID for every system at install time, and then later on when internet +is available, count the machine via this GUID. + +WDYT? +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001025.html">[Mageia-dev] test +</A></li> + <LI>Next message: <A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1027">[ date ]</a> + <a href="thread.html#1027">[ thread ]</a> + <a href="subject.html#1027">[ subject ]</a> + <a href="author.html#1027">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001028.html b/zarb-ml/mageia-dev/20101008/001028.html new file mode 100644 index 000000000..ae5b518d8 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001028.html @@ -0,0 +1,96 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Talk of Browsers + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Talk%20of%20Browsers&In-Reply-To=%3C4CAF222D.7070903%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001047.html"> + <LINK REL="Next" HREF="001030.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Talk of Browsers</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Talk%20of%20Browsers&In-Reply-To=%3C4CAF222D.7070903%40arcor.de%3E" + TITLE="[Mageia-dev] Talk of Browsers">doktor5000 at arcor.de + </A><BR> + <I>Fri Oct 8 15:52:45 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001030.html">[Mageia-dev] A new office suite ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1028">[ date ]</a> + <a href="thread.html#1028">[ thread ]</a> + <a href="subject.html#1028">[ subject ]</a> + <a href="author.html#1028">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> Am 01.10.2010 00:32, schrieb sorteal: +><i> I'm curious if Chromium has been considered as the default browser? With +</I>><i> KDE seeming to be the DE of choice and Firefox having a less than stellar +</I>><i> record with KDE integration I find Chromium to be an appealing alternative +</I>><i> to Firefox. Just curious. +</I>><i> +</I>><i> -Jason A. Turner +</I>><i> _______________________________________________ +</I>><i> Mageia-dev mailing list +</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">Mageia-dev at mageia.org</A> +</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">https://www.mageia.org/mailman/listinfo/mageia-dev</A> +</I>><i> +</I>Firefox got a lot of love reagrding integration, it uses KDE filepicker by +default, and it integrates +really nice with knotify and the notification system with the plasma-notify +extensions which is also +installed by default. What more do you need for good integration besides that? + +And please, don't make Chromium the default. It is still missing a lot of +useful extensions +which are available for Firefox, it is still under heavy development and a mess +to package +correctly, it needs huge and aggressive patches to use the system libraries +which need +to be rediffed often. It is fast and has some nice features that Firefox hasn't, +but please don't make it the default. +</PRE> + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001030.html">[Mageia-dev] A new office suite ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1028">[ date ]</a> + <a href="thread.html#1028">[ thread ]</a> + <a href="subject.html#1028">[ subject ]</a> + <a href="author.html#1028">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001029.html b/zarb-ml/mageia-dev/20101008/001029.html new file mode 100644 index 000000000..66ac7e36e --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001029.html @@ -0,0 +1,105 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] What do you think about create a Mageia Welcome Center? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3CAANLkTinb0Y4c%3DDzke_Gy7E%3DnL3Hi%2BT_c_L3ebc5%3DZmh%3D%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001027.html"> + <LINK REL="Next" HREF="001039.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] What do you think about create a Mageia Welcome Center?</H1> + <B>Gustavo Giampaoli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3CAANLkTinb0Y4c%3DDzke_Gy7E%3DnL3Hi%2BT_c_L3ebc5%3DZmh%3D%40mail.gmail.com%3E" + TITLE="[Mageia-dev] What do you think about create a Mageia Welcome Center?">giampaoli.gustavo at gmail.com + </A><BR> + <I>Fri Oct 8 16:07:56 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1029">[ date ]</a> + <a href="thread.html#1029">[ thread ]</a> + <a href="subject.html#1029">[ subject ]</a> + <a href="author.html#1029">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><i> What would be interesting is to count the mageia installations. Create +</I>><i> a GUID for every system at install time, and then later on when internet +</I>><i> is available, count the machine via this GUID. +</I> +Maybe, when it boots the first time, it could ask the user if he/she +likes to collaborate with mageia allowing to send anonymous +information about his/her system. + +If users accept, you can collect info about: + +* version (mageia 2011.0 64 bits... don't know if we'll have kind of +"one" and "free", but this also can be collected) +* first boot date +* hardware +* country +* gender (if during user configuration you could select if you are man or woman) +* age (idem gender) +* package selection: when you install Mandriva, you can select if +you'll use your system for Internet, server, development, etc. Also, +you can make your own and custom package selection. Can collect what +packages the users selected for the install. +* Optional: e-mail. So, if in anytime a user sends an e-mail from the +registered e-mail, saying "please, remove my info from your data base, +you can delete it". No e-mail, no right to ask for removing. + +This way, you can have a users map knowing how are they distributed +around the world. + +You can know if most people install for Internet or development or server. + +You can know if most users are man, or woman. If most are teens, adults. + +If most people install in notebooks, desktops, servers. + +And, of course, the note saying "you can disable this going to bla bla bla". + +Cheers! + + +Gustavo Giampaoli (aka tavillo1980) +</PRE> + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1029">[ date ]</a> + <a href="thread.html#1029">[ thread ]</a> + <a href="subject.html#1029">[ subject ]</a> + <a href="author.html#1029">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001030.html b/zarb-ml/mageia-dev/20101008/001030.html new file mode 100644 index 000000000..b11060e97 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001030.html @@ -0,0 +1,100 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] A new office suite ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20A%20new%20office%20suite%20%3F&In-Reply-To=%3C4CAF30A4.7010507%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001028.html"> + <LINK REL="Next" HREF="001031.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] A new office suite ?</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20A%20new%20office%20suite%20%3F&In-Reply-To=%3C4CAF30A4.7010507%40arcor.de%3E" + TITLE="[Mageia-dev] A new office suite ?">doktor5000 at arcor.de + </A><BR> + <I>Fri Oct 8 16:54:28 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A></li> + <LI>Next message: <A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1030">[ date ]</a> + <a href="thread.html#1030">[ thread ]</a> + <a href="subject.html#1030">[ subject ]</a> + <a href="author.html#1030">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> Am 07.10.2010 08:22, schrieb Mihai Dobrescu: +><i> +</I>><i> +</I>><i> If you have ever tried to rebuild/package the whole OOo, then you wouldn't +</I>><i> put that out so lightly. Ahmad really has a point there. Full OOo takes +</I>><i> up to 24 +</I>><i> hours building time and space requirements are in the region of 20-35 GB IIRC +</I>><i> on a desktop machine. +</I>><i> +</I>><i> ... +</I>><i> +</I>><i> BTW, i'm all for LibreOffice! +</I>><i> +</I>><i> Regards +</I>><i> +</I>><i> Florian Hubold +</I>><i> +</I>><i> +</I>><i> What kind of desktop machine (i.e. CPU, RAM specs)? +</I>><i> I'm with LibreOffice too (has similar story to Mageia after all ;)). +</I>That was my workstation 2 years ago, P4 2GHz, 1GB RAM. +But Ghiuseppe Ghibo had the same problems, as OOo couldn't +be put through buildsystem because of various limitations +and problems with the build. + +So maybe you can also understand why the OOo version was +never the latest in mandriva, or not the same as the stable +OOo releases at the same time. But everyon in need could +grab official OOo tarballs and use them. + +Now let's get on topic again ... +</PRE> + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A></li> + <LI>Next message: <A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1030">[ date ]</a> + <a href="thread.html#1030">[ thread ]</a> + <a href="subject.html#1030">[ subject ]</a> + <a href="author.html#1030">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001031.html b/zarb-ml/mageia-dev/20101008/001031.html new file mode 100644 index 000000000..2539d8c0a --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001031.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C4CAF3922.8030605%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001030.html"> + <LINK REL="Next" HREF="001034.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>andré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C4CAF3922.8030605%40laposte.net%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">andr55 at laposte.net + </A><BR> + <I>Fri Oct 8 17:30:42 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001030.html">[Mageia-dev] A new office suite ? +</A></li> + <LI>Next message: <A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1031">[ date ]</a> + <a href="thread.html#1031">[ thread ]</a> + <a href="subject.html#1031">[ subject ]</a> + <a href="author.html#1031">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael Scherer a écrit : +><i> Le jeudi 07 octobre 2010 à 11:14 -0400, Greg Harris a écrit : +</I>><i> +</I>><i> +</I>>><i> I certainly agree, and mean no disrespect to you and other maintainers +</I>>><i> who generously contribute their time and energy. But the Mandriva +</I>>><i> implementation of backports is not a solution for those who want a +</I>>><i> continuously updated distro. It works for me and I appreciate that it's +</I>>><i> there. But if you are going to design a new and appealing alternative, +</I>>><i> the effort required to make backports really known and useful needs to +</I>>><i> be taken into account. +</I>>><i> +</I>><i> Well, that's a long running task. First, we have added meta data to +</I>><i> repository so we could design a better interface for the software ( ie, +</I>><i> how to detect that a packages is a backport and how to see a software is +</I>><i> a update, a test update, or something else ), then we need to implement +</I>><i> the soft, etc. +</I>><i> +</I>><i> You spoke of having backport by default. We used to do it, but too much +</I>><i> people faced issue and complained. So we 1) said the truth, aka backport +</I>><i> didn't have the same rigorous testing 2) disabled it by default. +</I>><i> +</I>><i> Now, if things change ( ie, if we have a process with more QA ), we can +</I>><i> change again. +</I>><i> +</I>Backports are definitely an area needing improvement. Firstly, it is a +bit awkward - especially with the waiting for Rpmdrake to process - to +temporarily access backports. +And when I have, most of the time what I was interested in was not as up +to date as the developper's site, if there was a backport for the +application (or type of application) in question. +Luckily, being a programmer, it is not problematic for me to compile and +create menu entries, etc, if necessary. But that doesn't help ordinary +users of (now) Mageia. +So I intend to become more involved with backports - and trying to +improve Rpmdrake and other tools. +(If only Perl were a little easier/ more like other languages, I would +have already done more.) +So Mageia is pushing me to contribute more actively - hopefully others +as well. + +- André (andre999) + +</PRE> + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001030.html">[Mageia-dev] A new office suite ? +</A></li> + <LI>Next message: <A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1031">[ date ]</a> + <a href="thread.html#1031">[ thread ]</a> + <a href="subject.html#1031">[ subject ]</a> + <a href="author.html#1031">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001032.html b/zarb-ml/mageia-dev/20101008/001032.html new file mode 100644 index 000000000..efc3c853d --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001032.html @@ -0,0 +1,67 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF59C5.6050707%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001022.html"> + <LINK REL="Next" HREF="001038.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF59C5.6050707%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 19:49:57 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1032">[ date ]</a> + <a href="thread.html#1032">[ thread ]</a> + <a href="subject.html#1032">[ subject ]</a> + <a href="author.html#1032">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> +</I>><i> +</I>><i> As it seems we keep going in circles on this Romain has arranged the +</I>><i> following so that the threads on this topic become more focussed: +</I>I'd read the thread previously, and checked the wiki page, but this is a +different issue. That wiki page is pretty much just a poll (who are +you, what do you do with your systems, what kind of release schedule do +you want). This proposal is independent of whether there's a rolling +release or not; it's about presenting the update process to the user in +a different way. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1032">[ date ]</a> + <a href="thread.html#1032">[ thread ]</a> + <a href="subject.html#1032">[ subject ]</a> + <a href="author.html#1032">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001033.html b/zarb-ml/mageia-dev/20101008/001033.html new file mode 100644 index 000000000..1062558ed --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001033.html @@ -0,0 +1,102 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF5C7C.5000605%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001026.html"> + <LINK REL="Next" HREF="001044.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF5C7C.5000605%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 20:01:32 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1033">[ date ]</a> + <a href="thread.html#1033">[ thread ]</a> + <a href="subject.html#1033">[ subject ]</a> + <a href="author.html#1033">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Luca Berra wrote: +><i> On Thu, Oct 07, 2010 at 07:49:29PM -0400, Frank Griffin wrote: +</I>>><i> I'd like to propose the following model for updating released versions: +</I>>><i> +</I>>><i> 1) Users should not have to see, except in minor ways, the different +</I>>><i> repositories. Urpmi may see them, and advanced or ideologically polar +</I>>><i> users may care about them (e.g. free vs non-free), but most users +</I>><i> I object to this specific point, if what we are doing is free software +</I>><i> that should be made clear to users. and i believe the user shold be +</I>><i> asked wether they want to use only free software or not. +</I> +I have no objection to allowing users to check a box saying they want +free or mixed systems. I just don't want them to have to mess with a +repository to do it. + +><i> I just read it 3 times, and i still believe doing the above might +</I>><i> prove to be a +</I>><i> nightmare. +</I>><i> rolling back a single, well identified change is a doable task. +</I>><i> rolling back proceduraly a complex change becomes exponentially complex +</I>><i> even for experienced system engineers, let alone a piece of software. +</I> +I agree that the work becomes exponentially complex, but not the concept +of what has to be done. After all, what can be installed in an +automated way can be uninstalled. + +In any case, I would think that the primary use of this facility would +be to uninstall a single package. Urpme already knows how to do that, +and (provided you have the older RPM around) urpmi knows how to install +the old one. We expect users who want to roll back a package to do that +manually today. + +The problem is that removing the new package, if it provides something +that lots of things require, will want to uninstall a large number of +packages uselessly, because it doesn't know that you're about to turn +around and install something else that provides it. All I'm suggesting +is that + (a) we make the older RPMs available somewhere + (b) we automate the process to save three manual steps, and + (c) we wrap them in an atomic transaction (or what looks like one to +the user) to solve the problem above +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1033">[ date ]</a> + <a href="thread.html#1033">[ thread ]</a> + <a href="subject.html#1033">[ subject ]</a> + <a href="author.html#1033">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001034.html b/zarb-ml/mageia-dev/20101008/001034.html new file mode 100644 index 000000000..7a87955dd --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001034.html @@ -0,0 +1,119 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010081816.29518.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001031.html"> + <LINK REL="Next" HREF="001035.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010081816.29518.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">bgmilne at multilinks.com + </A><BR> + <I>Fri Oct 8 19:16:29 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1034">[ date ]</a> + <a href="thread.html#1034">[ thread ]</a> + <a href="subject.html#1034">[ subject ]</a> + <a href="author.html#1034">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Friday, 8 October 2010 16:30:42 andré wrote: +><i> Michael Scherer a écrit : +</I>><i> > Le jeudi 07 octobre 2010 à 11:14 -0400, Greg Harris a écrit : +</I>><i> >> I certainly agree, and mean no disrespect to you and other maintainers +</I>><i> >> who generously contribute their time and energy. But the Mandriva +</I>><i> >> implementation of backports is not a solution for those who want a +</I>><i> >> continuously updated distro. It works for me and I appreciate that it's +</I>><i> >> there. But if you are going to design a new and appealing alternative, +</I>><i> >> the effort required to make backports really known and useful needs to +</I>><i> >> be taken into account. +</I>><i> > +</I>><i> > Well, that's a long running task. First, we have added meta data to +</I>><i> > repository so we could design a better interface for the software ( ie, +</I>><i> > how to detect that a packages is a backport and how to see a software is +</I>><i> > a update, a test update, or something else ), then we need to implement +</I>><i> > the soft, etc. +</I>><i> > +</I>><i> > You spoke of having backport by default. We used to do it, but too much +</I>><i> > people faced issue and complained. So we 1) said the truth, aka backport +</I>><i> > didn't have the same rigorous testing 2) disabled it by default. +</I>><i> > +</I>><i> > Now, if things change ( ie, if we have a process with more QA ), we can +</I>><i> > change again. +</I>><i> +</I>><i> Backports are definitely an area needing improvement. Firstly, it is a +</I>><i> bit awkward - especially with the waiting for Rpmdrake to process - to +</I>><i> temporarily access backports. +</I> +I thought you could just select the backports dropdown? If not, maybe you +should rather use 'urpmi --searchmedia Backports <packagename>'. + +Anyway, this isn't an issue with the "release cycle" aspect, it is a UI/design +problem in rpmdrake. + +><i> And when I have, most of the time what I was interested in was not as up +</I>><i> to date as the developper's site, if there was a backport for the +</I>><i> application (or type of application) in question. +</I> +Was it up-to-date in cooker? If not, this is probably purely a man-power +problem. If it was, did you request a backport? As I mentioned before, I think +one shortcoming of backports was knowing what packages people were interested +in having backported. + +But, I know of many instances where backports were requested on IRC, and +provided within under an hour (on the fast mirrors). + +><i> Luckily, being a programmer, it is not problematic for me to compile and +</I>><i> create menu entries, etc, if necessary. +</I> +There's no reason you should waste time that could be better spent. In some +cases, pushing a backport takes all of 2 minutes. + +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1034">[ date ]</a> + <a href="thread.html#1034">[ thread ]</a> + <a href="subject.html#1034">[ subject ]</a> + <a href="author.html#1034">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001035.html b/zarb-ml/mageia-dev/20101008/001035.html new file mode 100644 index 000000000..b60f213a5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001035.html @@ -0,0 +1,75 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [Mageia] Will Mageia offer MeeGo ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%5D%20Will%20Mageia%20offer%20MeeGo%20%3F&In-Reply-To=%3C4CAF6297.40301%40free.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001034.html"> + <LINK REL="Next" HREF="001036.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [Mageia] Will Mageia offer MeeGo ?</H1> + <B>Cassian Braconnnier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%5D%20Will%20Mageia%20offer%20MeeGo%20%3F&In-Reply-To=%3C4CAF6297.40301%40free.fr%3E" + TITLE="[Mageia-dev] [Mageia] Will Mageia offer MeeGo ?">ptyxs at free.fr + </A><BR> + <I>Fri Oct 8 20:27:35 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1035">[ date ]</a> + <a href="thread.html#1035">[ thread ]</a> + <a href="subject.html#1035">[ subject ]</a> + <a href="author.html#1035">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Fedora 14 (actually a bêta) will offer MeeGo 1.0 as a desktop, an a par +with KDE, GNOME, LXDE etc. +Will Mageia offet it too ? +Cassian (ptyxs) + + + + +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1035">[ date ]</a> + <a href="thread.html#1035">[ thread ]</a> + <a href="subject.html#1035">[ subject ]</a> + <a href="author.html#1035">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001036.html b/zarb-ml/mageia-dev/20101008/001036.html new file mode 100644 index 000000000..013705c48 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001036.html @@ -0,0 +1,78 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [Mageia] Will Mageia offer MeeGo ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%5D%20Will%20Mageia%20offer%20MeeGo%20%3F&In-Reply-To=%3C4CAF6476.6080900%40free.fr%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001035.html"> + <LINK REL="Next" HREF="001037.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [Mageia] Will Mageia offer MeeGo ?</H1> + <B>Cassian Braconnnier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%5D%20Will%20Mageia%20offer%20MeeGo%20%3F&In-Reply-To=%3C4CAF6476.6080900%40free.fr%3E" + TITLE="[Mageia-dev] [Mageia] Will Mageia offer MeeGo ?">ptyxs at free.fr + </A><BR> + <I>Fri Oct 8 20:35:34 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI>Next message: <A HREF="001037.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1036">[ date ]</a> + <a href="thread.html#1036">[ thread ]</a> + <a href="subject.html#1036">[ subject ]</a> + <a href="author.html#1036">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 08/10/2010 20:27, Cassian Braconnnier a écrit : +><i> Fedora 14 (actually a bêta) will offer MeeGo 1.0 as a desktop, an a +</I>><i> par with KDE, GNOME, LXDE etc. +</I>><i> Will Mageia offet it too ? +</I>><i> Cassian (ptyxs) +</I>A relevant link : +<A HREF="http://fedoraproject.org/wiki/Features/MeeGo_1.0">http://fedoraproject.org/wiki/Features/MeeGo_1.0</A> + + + + +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI>Next message: <A HREF="001037.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1036">[ date ]</a> + <a href="thread.html#1036">[ thread ]</a> + <a href="subject.html#1036">[ subject ]</a> + <a href="author.html#1036">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001037.html b/zarb-ml/mageia-dev/20101008/001037.html new file mode 100644 index 000000000..6ecc4f2b4 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001037.html @@ -0,0 +1,77 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [Mageia] Will Mageia offer MeeGo ? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%5D%20Will%20Mageia%20offer%20MeeGo%20%3F&In-Reply-To=%3C4CAF65AF.6010505%40mrtomlinux.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001036.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [Mageia] Will Mageia offer MeeGo ?</H1> + <B>Thomas Canniot</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia%5D%20Will%20Mageia%20offer%20MeeGo%20%3F&In-Reply-To=%3C4CAF65AF.6010505%40mrtomlinux.org%3E" + TITLE="[Mageia-dev] [Mageia] Will Mageia offer MeeGo ?">thomas.canniot at mrtomlinux.org + </A><BR> + <I>Fri Oct 8 20:40:47 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1037">[ date ]</a> + <a href="thread.html#1037">[ thread ]</a> + <a href="subject.html#1037">[ subject ]</a> + <a href="author.html#1037">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 08/10/2010 20:27, Cassian Braconnnier a écrit : +><i> Fedora 14 (actually a bêta) will offer MeeGo 1.0 as a desktop, an a par +</I>><i> with KDE, GNOME, LXDE etc. +</I>><i> Will Mageia offet it too ? +</I>><i> Cassian (ptyxs) +</I> +I guess it will as long as Mageia Community is able to manage its +integration ;) + +Best regards, + +Thomas + +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1037">[ date ]</a> + <a href="thread.html#1037">[ thread ]</a> + <a href="subject.html#1037">[ subject ]</a> + <a href="author.html#1037">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001038.html b/zarb-ml/mageia-dev/20101008/001038.html new file mode 100644 index 000000000..5c73c521e --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001038.html @@ -0,0 +1,114 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8npuf%24c8u%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001032.html"> + <LINK REL="Next" HREF="001042.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8npuf%24c8u%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 21:03:42 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1038">[ date ]</a> + <a href="thread.html#1038">[ thread ]</a> + <a href="subject.html#1038">[ subject ]</a> + <a href="author.html#1038">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-08 13:49, Frank Griffin a écrit : +><i> Marc Paré wrote: +</I>>><i> +</I>>><i> +</I>>><i> As it seems we keep going in circles on this Romain has arranged the +</I>>><i> following so that the threads on this topic become more focussed: +</I>><i> I'd read the thread previously, and checked the wiki page, but this is a +</I>><i> different issue. That wiki page is pretty much just a poll (who are +</I>><i> you, what do you do with your systems, what kind of release schedule do +</I>><i> you want). This proposal is independent of whether there's a rolling +</I>><i> release or not; it's about presenting the update process to the user in +</I>><i> a different way. +</I>><i> +</I> +Yup, I reread your proposal. You are right. It would be nice for you to +add it to the wiki page. This is after all, as you said, one of the +issues raised in the thread. + +-------------------- + +As to your proposal, the issue with "Backports" and lack of +understanding form the users point of view is quite a large one. There +should be a VERY descriptive info section explaining the purpose of +"Backports". The lack of a descriptive expanation just did not make the +"Backports" section of the MCC popular by users. We just assumed that +when a newer version of our favourite soft. had come out, that all we +had to do is wait for it to come up in the "you know, that red ball +thingy in the tasbar on the right-bottom". + +I am now making use of Backports and loving it! But also realize the +dangers of using it. + +-------------------- + +So, as to your proposal, I am in agreement with it. Maybe a suggestion +(more of a question), seeing as the issues have to deal more with the +dependencies of a "roll-back", what if, "Backports" would install, +somehow the software updates in a self compartment kind of way (sorry my +language terms may not be descriptive enough). + +Users know that repositories are activated and some are not at the time +of install. I think that most users have a faint idea of this. But if +Backports were to be used more at the user level, what is clear, is +that, there should be a roll-back feature. If the roll-back feature, as +a normal course of rolling-back will or could remove other softs due to +dependencies, then maybe possible option would be to have the "Backport" +software installations install all dependencies in such a way as to +isolate them from the larger distro packages. This would in effect could +make a secondary related-dependency file on the system. Then if a +roll-back were done a Backported software package only the associated +dependencies would be deleted. + +Could this be done? + +Sorry, I am not sure if this is written clearly enough. + +Marc + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1038">[ date ]</a> + <a href="thread.html#1038">[ thread ]</a> + <a href="subject.html#1038">[ subject ]</a> + <a href="author.html#1038">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001039.html b/zarb-ml/mageia-dev/20101008/001039.html new file mode 100644 index 000000000..478fdd263 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001039.html @@ -0,0 +1,82 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] What do you think about create a Mageia Welcome Center? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3C37b.4caf6b31%40mageia.linuxtech.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001029.html"> + <LINK REL="Next" HREF="001040.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] What do you think about create a Mageia Welcome Center?</H1> + <B>Tux99</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3C37b.4caf6b31%40mageia.linuxtech.net%3E" + TITLE="[Mageia-dev] What do you think about create a Mageia Welcome Center?">tux99-mga at uridium.org + </A><BR> + <I>Fri Oct 8 21:04:18 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1039">[ date ]</a> + <a href="thread.html#1039">[ thread ]</a> + <a href="subject.html#1039">[ subject ]</a> + <a href="author.html#1039">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> + +Quote: Florian Hubold wrote on Fri, 08 October 2010 15:46 +><i> +</I>><i> What would be interesting is to count the mageia installations. Create +</I>><i> a GUID for every system at install time, and then later on when +</I>><i> internet +</I>><i> is available, count the machine via this GUID. +</I>><i> +</I>><i> WDYT? +</I> +No way, that's way to Orwellian, it would give Mageia a really bad +reputation. + +A rough count of installs can be done by counting the number of unique IPs +accessing the updates, of course this won't be precise (proxies, etc) but +it should give a rough estimate, there is no need for precise numbers. + +-- +Mageia ML Forum Gateway: <A HREF="http://mageia.linuxtech.net/forum/">http://mageia.linuxtech.net/forum/</A> +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1039">[ date ]</a> + <a href="thread.html#1039">[ thread ]</a> + <a href="subject.html#1039">[ subject ]</a> + <a href="author.html#1039">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001040.html b/zarb-ml/mageia-dev/20101008/001040.html new file mode 100644 index 000000000..56c4e684b --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001040.html @@ -0,0 +1,90 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] What do you think about create a Mageia Welcome Center? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3Ci8nrki%24jl1%244%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001039.html"> + <LINK REL="Next" HREF="001041.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] What do you think about create a Mageia Welcome Center?</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3Ci8nrki%24jl1%244%40dough.gmane.org%3E" + TITLE="[Mageia-dev] What do you think about create a Mageia Welcome Center?">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 21:32:34 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1040">[ date ]</a> + <a href="thread.html#1040">[ thread ]</a> + <a href="subject.html#1040">[ subject ]</a> + <a href="author.html#1040">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-08 15:04, Tux99 a écrit : +><i> +</I>><i> +</I>><i> Quote: Florian Hubold wrote on Fri, 08 October 2010 15:46 +</I>>><i> +</I>>><i> What would be interesting is to count the mageia installations. Create +</I>>><i> a GUID for every system at install time, and then later on when +</I>>><i> internet +</I>>><i> is available, count the machine via this GUID. +</I>>><i> +</I>>><i> WDYT? +</I>><i> +</I>><i> No way, that's way to Orwellian, it would give Mageia a really bad +</I>><i> reputation. +</I>><i> +</I>><i> A rough count of installs can be done by counting the number of unique IPs +</I>><i> accessing the updates, of course this won't be precise (proxies, etc) but +</I>><i> it should give a rough estimate, there is no need for precise numbers. +</I>><i> +</I> +I agree, in this case a rough count is good enough. + +We all remember the Intel ID system where you could be identified at +chip level through the BIOS. Scary business. A distro could have denied +you installation just based on your chip ID. + +Marc + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1040">[ date ]</a> + <a href="thread.html#1040">[ thread ]</a> + <a href="subject.html#1040">[ subject ]</a> + <a href="author.html#1040">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001041.html b/zarb-ml/mageia-dev/20101008/001041.html new file mode 100644 index 000000000..19200362d --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001041.html @@ -0,0 +1,93 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] What do you think about create a Mageia Welcome Center? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3Ci8nsbq%24ts0%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001040.html"> + <LINK REL="Next" HREF="001047.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] What do you think about create a Mageia Welcome Center?</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%09Center%3F&In-Reply-To=%3Ci8nsbq%24ts0%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] What do you think about create a Mageia Welcome Center?">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 21:44:57 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1041">[ date ]</a> + <a href="thread.html#1041">[ thread ]</a> + <a href="subject.html#1041">[ subject ]</a> + <a href="author.html#1041">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-08 09:46, Florian Hubold a écrit : +><i> Am 30.09.2010 12:34, schrieb Olivier Méjean: +</I>>><i> Le jeudi 30 septembre 2010 12:19:43, Robert Xu a écrit : +</I>>><i> Is a survey necessary ? +</I>>><i> +</I>><i> It's not really necessary. For example, in mandriva my laptop had no +</I>><i> internet +</I>><i> when booting the first time, as my wireless needs a firmware. So i never +</I>><i> completed the survey, and as it only started on the first boot, mandriva +</I>><i> never got any real data from me. Maybe when the infrastructure is up +</I>><i> and some releases were made, this can be discussed again. +</I>><i> +</I> +For these installations, there could be a case made for preparing an +initial form, with the users consent of course, that could be +transmitted later, again with user knowledge and consent. + +It is still to Mageia's advantage, both from a development point of view +and marketing point of view, to be aware of the instances of installations. + +It doesn't have to be an accurate amount, for that matter, it could be +an approximation of the amount of installations. This could also be done +at the point of download monitoring, as suggested elsewhere, with unique +IP's being taken into account. + +I am more in favour of doing both, but more interested of the "at +installation" and filling a short survey for Mageia stat purposes. This +is a more concrete way measuring user participation in the project. + +Marc + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1041">[ date ]</a> + <a href="thread.html#1041">[ thread ]</a> + <a href="subject.html#1041">[ subject ]</a> + <a href="author.html#1041">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001042.html b/zarb-ml/mageia-dev/20101008/001042.html new file mode 100644 index 000000000..9cc349e18 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001042.html @@ -0,0 +1,97 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF77F5.3070309%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001038.html"> + <LINK REL="Next" HREF="001043.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF77F5.3070309%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 21:58:45 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1042">[ date ]</a> + <a href="thread.html#1042">[ thread ]</a> + <a href="subject.html#1042">[ subject ]</a> + <a href="author.html#1042">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> So, as to your proposal, I am in agreement with it. Maybe a suggestion +</I>><i> (more of a question), seeing as the issues have to deal more with the +</I>><i> dependencies of a "roll-back", what if, "Backports" would install, +</I>><i> somehow the software updates in a self compartment kind of way (sorry +</I>><i> my language terms may not be descriptive enough). +</I> +Michael hinted at that, either taking a copy-on-write (brtfs) copy of +the user's system for later restore, or having users install the update +on a VM copy of their system, but the image thing is good for only one +update at a time, and I don't think most users are going to re-install +in a VM to test a new package. There really isn't a good way to install +in a "sandbox". + +><i> +</I>><i> Users know that repositories are activated and some are not at the +</I>><i> time of install. I think that most users have a faint idea of this. +</I>><i> But if Backports were to be used more at the user level, what is +</I>><i> clear, is that, there should be a roll-back feature. If the roll-back +</I>><i> feature, as a normal course of rolling-back will or could remove other +</I>><i> softs due to dependencies, then maybe possible option would be to have +</I>><i> the "Backport" software installations install all dependencies in such +</I>><i> a way as to isolate them from the larger distro packages. This would +</I>><i> in effect could make a secondary related-dependency file on the +</I>><i> system. Then if a roll-back were done a Backported software package +</I>><i> only the associated dependencies would be deleted. +</I>><i> +</I>><i> Could this be done? +</I> +Wherever this can be done, it usually is. Multiple versions of +libraries can coexist in Linux, so if the new version requires new +libraries, there's no conflict. + +The dependencies that cause problems are, for example, the situation +where you can only have one of a certain service provider and its users +are bound to it by an API which changes between the release version and +the new version you want to install. For example, if A, B, C, D, E all +use F, and the new version of C has been changed to use the +(incompatible) API of the new version of F, you'd have to install all 6. + + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1042">[ date ]</a> + <a href="thread.html#1042">[ thread ]</a> + <a href="subject.html#1042">[ subject ]</a> + <a href="author.html#1042">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001043.html b/zarb-ml/mageia-dev/20101008/001043.html new file mode 100644 index 000000000..8fdac08a5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001043.html @@ -0,0 +1,85 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8nts1%2497t%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001042.html"> + <LINK REL="Next" HREF="001045.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8nts1%2497t%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 22:10:40 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1043">[ date ]</a> + <a href="thread.html#1043">[ thread ]</a> + <a href="subject.html#1043">[ subject ]</a> + <a href="author.html#1043">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +><i> +</I>><i> Wherever this can be done, it usually is. Multiple versions of +</I>><i> libraries can coexist in Linux, so if the new version requires new +</I>><i> libraries, there's no conflict. +</I>><i> +</I>><i> The dependencies that cause problems are, for example, the situation +</I>><i> where you can only have one of a certain service provider and its users +</I>><i> are bound to it by an API which changes between the release version and +</I>><i> the new version you want to install. For example, if A, B, C, D, E all +</I>><i> use F, and the new version of C has been changed to use the +</I>><i> (incompatible) API of the new version of F, you'd have to install all 6. +</I>><i> +</I>><i> +</I>><i> +</I> +So, in terms of space used for this, if you had to install all 6, would +this tax the system so much and risk filling up the hardrive needlessly. + +If not, would this cause your installation to misbehave. + +It not, if a rollback were done, could all 6 as well as the new F be +removed and the old version restored? + +If this is possible, would this have an impact on devs preparing +Backport versions with rollbacks? + +Marc + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1043">[ date ]</a> + <a href="thread.html#1043">[ thread ]</a> + <a href="subject.html#1043">[ subject ]</a> + <a href="author.html#1043">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001044.html b/zarb-ml/mageia-dev/20101008/001044.html new file mode 100644 index 000000000..b74ceec97 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001044.html @@ -0,0 +1,79 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010082217.04493.r.h.michel%2Bmageia%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001033.html"> + <LINK REL="Next" HREF="001046.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Renaud MICHEL</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010082217.04493.r.h.michel%2Bmageia%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">r.h.michel+mageia at gmail.com + </A><BR> + <I>Fri Oct 8 22:17:04 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1044">[ date ]</a> + <a href="thread.html#1044">[ thread ]</a> + <a href="subject.html#1044">[ subject ]</a> + <a href="author.html#1044">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On vendredi 08 octobre 2010 at 20:01, Frank Griffin wrote : +><i> The problem is that removing the new package, if it provides something +</I>><i> that lots of things require, will want to uninstall a large number of +</I>><i> packages uselessly, because it doesn't know that you're about to turn +</I>><i> around and install something else that provides it. All I'm suggesting +</I>><i> is that +</I>><i> (a) we make the older RPMs available somewhere +</I>><i> (b) we automate the process to save three manual steps, and +</I>><i> (c) we wrap them in an atomic transaction (or what looks like one to +</I>><i> the user) to solve the problem above +</I> +If you still have the old package (which could have been reconstructed with +the --repackage option of urpmi), rpm can upgrade to an older version using +the --oldpackage option. So, if the dependencies are sill met with the old +package you won't have the uninstall problem. + +I don't think urpmi support that, but if rpm can do it, it should not be to +hard to add it to urpmi. + +-- +Renaud Michel +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1044">[ date ]</a> + <a href="thread.html#1044">[ thread ]</a> + <a href="subject.html#1044">[ subject ]</a> + <a href="author.html#1044">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001045.html b/zarb-ml/mageia-dev/20101008/001045.html new file mode 100644 index 000000000..5ecf1388b --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001045.html @@ -0,0 +1,102 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF7FC3.50805%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001043.html"> + <LINK REL="Next" HREF="001048.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF7FC3.50805%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 22:32:03 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1045">[ date ]</a> + <a href="thread.html#1045">[ thread ]</a> + <a href="subject.html#1045">[ subject ]</a> + <a href="author.html#1045">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> +</I>><i> So, in terms of space used for this, if you had to install all 6, +</I>><i> would this tax the system so much and risk filling up the hardrive +</I>><i> needlessly. +</I> +Not really, since the old versions would be removed when the new ones +were installed. The behavior I described is not part of the proposal; +that's what happens today. + +><i> +</I>><i> It not, if a rollback were done, could all 6 as well as the new F be +</I>><i> removed and the old version restored? +</I> +Yes, that's exactly what happens today.The problem is that today, +removing them may cause tons of other packages to have to be removed +because they require things that A-F provide. This wasn't a problem on +upgrade, because the removal of the old and the addition of the new was +a single urpmi "transaction" (I put this in quotes because urpmi uses +"transaction" to mean something other than what I mean here), and urpmi +"knew" that the new versions supplied all the things that vanished when +the old versions were removed. Today, rollbacks have to be done +manually - remove new, then install old. Urpmi doesn't know at the time +of the removal that you're going to turn around and install the old +versions next. It only sees that all the things that both the old and +new versions supply are about to disappear from your system, so it tells +you that you have to remove any other package which requires those things. +><i> +</I>><i> If this is possible, would this have an impact on devs preparing +</I>><i> Backport versions with rollbacks? +</I> +RPM dependencies aren't a problem. Urpmi/urpme know all about them. +The only packaging changes would be for situations like that where a new +version of an application has changed a format of one of its files in +your home directory and the new version automatically converts the old +version of the file to the new format. In that case, the package would +need install scriptlets that copied the old version somewhere so that it +could be restored at uninstall time, otherwise the old version of the +software won't be able to use the new file format. + +The biggest chunk of development involved in the proposal is to make +urpmi do a rollback as a single operation, just as it does an upgrade. +This already exists, in a way; there is a facility called urpmi.recover +that does this type of thing. Bit it's not really considered +mainstream, and I don't think it's been supported for a while. + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1045">[ date ]</a> + <a href="thread.html#1045">[ thread ]</a> + <a href="subject.html#1045">[ subject ]</a> + <a href="author.html#1045">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001046.html b/zarb-ml/mageia-dev/20101008/001046.html new file mode 100644 index 000000000..170274aaa --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001046.html @@ -0,0 +1,66 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF8059.30202%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001044.html"> + <LINK REL="Next" HREF="001023.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF8059.30202%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Fri Oct 8 22:34:33 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1046">[ date ]</a> + <a href="thread.html#1046">[ thread ]</a> + <a href="subject.html#1046">[ subject ]</a> + <a href="author.html#1046">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Renaud MICHEL wrote: +><i> If you still have the old package (which could have been reconstructed with +</I>><i> the --repackage option of urpmi), rpm can upgrade to an older version using +</I>><i> the --oldpackage option. So, if the dependencies are sill met with the old +</I>><i> package you won't have the uninstall problem. +</I>><i> +</I>><i> I don't think urpmi support that, but if rpm can do it, it should not be to +</I>><i> hard to add it to urpmi. +</I>><i> +</I>Exactly. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1046">[ date ]</a> + <a href="thread.html#1046">[ thread ]</a> + <a href="subject.html#1046">[ subject ]</a> + <a href="author.html#1046">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001047.html b/zarb-ml/mageia-dev/20101008/001047.html new file mode 100644 index 000000000..c218c74df --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001047.html @@ -0,0 +1,68 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] What do you think about create a Mageia Welcome Center? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%20Center%3F&In-Reply-To=%3Cop.vj9yqlfhn7mcit%40hodgins.homeip.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001041.html"> + <LINK REL="Next" HREF="001028.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] What do you think about create a Mageia Welcome Center?</H1> + <B>David W. Hodgins</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20What%20do%20you%20think%20about%20create%20a%20Mageia%20Welcome%0A%20Center%3F&In-Reply-To=%3Cop.vj9yqlfhn7mcit%40hodgins.homeip.net%3E" + TITLE="[Mageia-dev] What do you think about create a Mageia Welcome Center?">davidwhodgins at gmail.com + </A><BR> + <I>Fri Oct 8 22:48:11 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1047">[ date ]</a> + <a href="thread.html#1047">[ thread ]</a> + <a href="subject.html#1047">[ subject ]</a> + <a href="author.html#1047">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Fri, 08 Oct 2010 09:46:38 -0400, Florian Hubold <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">doktor5000 at arcor.de</A>> wrote: + +><i> What would be interesting is to count the mageia installations. Create +</I>><i> a GUID for every system at install time, and then later on when internet +</I>><i> is available, count the machine via this GUID. +</I> +I don't think a GUID would be very useful. When I installed Mandriva, I +installed it on one machine, setup the configurations the way I wanted +them, and then cloned the hd for 4 other systems. The GUID would be +identical on all four systems. + +Regards, Dave Hodgins +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A></li> + <LI>Next message: <A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1047">[ date ]</a> + <a href="thread.html#1047">[ thread ]</a> + <a href="subject.html#1047">[ subject ]</a> + <a href="author.html#1047">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/001048.html b/zarb-ml/mageia-dev/20101008/001048.html new file mode 100644 index 000000000..cec10f786 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/001048.html @@ -0,0 +1,114 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8o03u%24p72%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001045.html"> + <LINK REL="Next" HREF="001024.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8o03u%24p72%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Fri Oct 8 22:49:01 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1048">[ date ]</a> + <a href="thread.html#1048">[ thread ]</a> + <a href="subject.html#1048">[ subject ]</a> + <a href="author.html#1048">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-08 16:32, Frank Griffin a écrit : +><i> Marc Paré wrote: +</I>>><i> +</I>>><i> So, in terms of space used for this, if you had to install all 6, +</I>>><i> would this tax the system so much and risk filling up the hardrive +</I>>><i> needlessly. +</I>><i> +</I>><i> Not really, since the old versions would be removed when the new ones +</I>><i> were installed. The behavior I described is not part of the proposal; +</I>><i> that's what happens today. +</I>><i> +</I>>><i> +</I>>><i> It not, if a rollback were done, could all 6 as well as the new F be +</I>>><i> removed and the old version restored? +</I>><i> +</I>><i> Yes, that's exactly what happens today.The problem is that today, +</I>><i> removing them may cause tons of other packages to have to be removed +</I>><i> because they require things that A-F provide. This wasn't a problem on +</I>><i> upgrade, because the removal of the old and the addition of the new was +</I>><i> a single urpmi "transaction" (I put this in quotes because urpmi uses +</I>><i> "transaction" to mean something other than what I mean here), and urpmi +</I>><i> "knew" that the new versions supplied all the things that vanished when +</I>><i> the old versions were removed. Today, rollbacks have to be done +</I>><i> manually - remove new, then install old. Urpmi doesn't know at the time +</I>><i> of the removal that you're going to turn around and install the old +</I>><i> versions next. It only sees that all the things that both the old and +</I>><i> new versions supply are about to disappear from your system, so it tells +</I>><i> you that you have to remove any other package which requires those things. +</I>>><i> +</I>>><i> If this is possible, would this have an impact on devs preparing +</I>>><i> Backport versions with rollbacks? +</I>><i> +</I>><i> RPM dependencies aren't a problem. Urpmi/urpme know all about them. +</I>><i> The only packaging changes would be for situations like that where a new +</I>><i> version of an application has changed a format of one of its files in +</I>><i> your home directory and the new version automatically converts the old +</I>><i> version of the file to the new format. In that case, the package would +</I>><i> need install scriptlets that copied the old version somewhere so that it +</I>><i> could be restored at uninstall time, otherwise the old version of the +</I>><i> software won't be able to use the new file format. +</I>><i> +</I>><i> The biggest chunk of development involved in the proposal is to make +</I>><i> urpmi do a rollback as a single operation, just as it does an upgrade. +</I>><i> This already exists, in a way; there is a facility called urpmi.recover +</I>><i> that does this type of thing. Bit it's not really considered +</I>><i> mainstream, and I don't think it's been supported for a while. +</I>><i> +</I>><i> +</I> +Thanks. So this thread is to see if there were a possibility to +programme a more efficient roll-back option so that it would be more +"aware" of the previous "dependencies" needs for the previous version. +Having "double dependencies" is not so much of a problem, it is the +rollback to a previous version where the dependency confusion may occur, +and, ONLY, if an upgraded type of "dependency" thread had been +installed. (Sorry I may have used the wrong terms in the last sentence). + +Marc + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1048">[ date ]</a> + <a href="thread.html#1048">[ thread ]</a> + <a href="subject.html#1048">[ subject ]</a> + <a href="author.html#1048">[ 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> diff --git a/zarb-ml/mageia-dev/20101008/author.html b/zarb-ml/mageia-dev/20101008/author.html new file mode 100644 index 000000000..55b2a4ed5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/author.html @@ -0,0 +1,192 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 8 October 2010 Archive by author</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>8 October 2010 Archives by author</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Fri Oct 8 00:29:57 CEST 2010</i><br> + <b>Ending:</b> <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Messages:</b> 29<p> + <ul> + +<LI><A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1024"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1035"> </A> +<I>Cassian Braconnnier +</I> + +<LI><A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1036"> </A> +<I>Cassian Braconnnier +</I> + +<LI><A HREF="001037.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1037"> </A> +<I>Thomas Canniot +</I> + +<LI><A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1029"> </A> +<I>Gustavo Giampaoli +</I> + +<LI><A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1021"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1032"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1033"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1042"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1045"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1046"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1047"> </A> +<I>David W. Hodgins +</I> + +<LI><A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1027"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1028"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001030.html">[Mageia-dev] A new office suite ? +</A><A NAME="1030"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001020.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1020"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1044"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1034"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001025.html">[Mageia-dev] test +</A><A NAME="1025"> </A> +<I>Angelo Naselli +</I> + +<LI><A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1023"> </A> +<I>Fernando Parra +</I> + +<LI><A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1022"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1038"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1040"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1041"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1043"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1048"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1026"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1039"> </A> +<I>Tux99 +</I> + +<LI><A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1031"> </A> +<I>andré +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Archived on:</b> <i>Fri Oct 8 22:49:17 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101008/date.html b/zarb-ml/mageia-dev/20101008/date.html new file mode 100644 index 000000000..b7ff77c95 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/date.html @@ -0,0 +1,192 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 8 October 2010 Archive by date</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>8 October 2010 Archives by date</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Fri Oct 8 00:29:57 CEST 2010</i><br> + <b>Ending:</b> <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Messages:</b> 29<p> + <ul> + +<LI><A HREF="001020.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1020"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1021"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1022"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1023"> </A> +<I>Fernando Parra +</I> + +<LI><A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1024"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001025.html">[Mageia-dev] test +</A><A NAME="1025"> </A> +<I>Angelo Naselli +</I> + +<LI><A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1026"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1027"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1028"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1029"> </A> +<I>Gustavo Giampaoli +</I> + +<LI><A HREF="001030.html">[Mageia-dev] A new office suite ? +</A><A NAME="1030"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1031"> </A> +<I>andré +</I> + +<LI><A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1034"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1032"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1033"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1035"> </A> +<I>Cassian Braconnnier +</I> + +<LI><A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1036"> </A> +<I>Cassian Braconnnier +</I> + +<LI><A HREF="001037.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1037"> </A> +<I>Thomas Canniot +</I> + +<LI><A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1038"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1039"> </A> +<I>Tux99 +</I> + +<LI><A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1040"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1041"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1042"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1043"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1044"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1045"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1046"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1047"> </A> +<I>David W. Hodgins +</I> + +<LI><A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1048"> </A> +<I>Marc Paré +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Archived on:</b> <i>Fri Oct 8 22:49:17 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101008/index.html b/zarb-ml/mageia-dev/20101008/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/20101008/subject.html b/zarb-ml/mageia-dev/20101008/subject.html new file mode 100644 index 000000000..6b6620d3a --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/subject.html @@ -0,0 +1,192 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 8 October 2010 Archive by subject</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>8 October 2010 Archives by subject</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Fri Oct 8 00:29:57 CEST 2010</i><br> + <b>Ending:</b> <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Messages:</b> 29<p> + <ul> + +<LI><A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1035"> </A> +<I>Cassian Braconnnier +</I> + +<LI><A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1036"> </A> +<I>Cassian Braconnnier +</I> + +<LI><A HREF="001037.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1037"> </A> +<I>Thomas Canniot +</I> + +<LI><A HREF="001030.html">[Mageia-dev] A new office suite ? +</A><A NAME="1030"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1023"> </A> +<I>Fernando Parra +</I> + +<LI><A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1031"> </A> +<I>andré +</I> + +<LI><A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1034"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1021"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1022"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1024"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1026"> </A> +<I>Michael Scherer +</I> + +<LI><A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1032"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1033"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1038"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1042"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1043"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1044"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1045"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1046"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1048"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001020.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1020"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1028"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001025.html">[Mageia-dev] test +</A><A NAME="1025"> </A> +<I>Angelo Naselli +</I> + +<LI><A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1029"> </A> +<I>Gustavo Giampaoli +</I> + +<LI><A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1039"> </A> +<I>Tux99 +</I> + +<LI><A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1040"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1041"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1027"> </A> +<I>Florian Hubold +</I> + +<LI><A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1047"> </A> +<I>David W. Hodgins +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Archived on:</b> <i>Fri Oct 8 22:49:17 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101008/thread.html b/zarb-ml/mageia-dev/20101008/thread.html new file mode 100644 index 000000000..da32c967f --- /dev/null +++ b/zarb-ml/mageia-dev/20101008/thread.html @@ -0,0 +1,239 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 8 October 2010 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>8 October 2010 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Fri Oct 8 00:29:57 CEST 2010</i><br> + <b>Ending:</b> <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Messages:</b> 29<p> + <ul> + +<!--0 01286490597- --> +<LI><A HREF="001020.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1020"> </A> +<I>Renaud MICHEL +</I> + +<!--0 01286495369- --> +<LI><A HREF="001021.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1021"> </A> +<I>Frank Griffin +</I> + +<UL> +<!--1 01286495369-01286501399- --> +<LI><A HREF="001022.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1022"> </A> +<I>Marc Paré +</I> + +<UL> +<!--2 01286495369-01286501399-01286560197- --> +<LI><A HREF="001032.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1032"> </A> +<I>Frank Griffin +</I> + +<UL> +<!--3 01286495369-01286501399-01286560197-01286564622- --> +<LI><A HREF="001038.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1038"> </A> +<I>Marc Paré +</I> + +<!--3 01286495369-01286501399-01286560197-01286564622-01286567925- --> +<LI><A HREF="001042.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1042"> </A> +<I>Frank Griffin +</I> + +<!--3 01286495369-01286501399-01286560197-01286564622-01286567925-01286568640- --> +<LI><A HREF="001043.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1043"> </A> +<I>Marc Paré +</I> + +<!--3 01286495369-01286501399-01286560197-01286564622-01286567925-01286568640-01286569923- --> +<LI><A HREF="001045.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1045"> </A> +<I>Frank Griffin +</I> + +<!--3 01286495369-01286501399-01286560197-01286564622-01286567925-01286568640-01286569923-01286570941- --> +<LI><A HREF="001048.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1048"> </A> +<I>Marc Paré +</I> + +</UL> +</UL> +<!--1 01286495369-01286523369- --> +<LI><A HREF="001024.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1024"> </A> +<I>Luca Berra +</I> + +<UL> +<!--2 01286495369-01286523369-01286537531- --> +<LI><A HREF="001026.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1026"> </A> +<I>Michael Scherer +</I> + +<!--2 01286495369-01286523369-01286560892- --> +<LI><A HREF="001033.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1033"> </A> +<I>Frank Griffin +</I> + +<UL> +<!--3 01286495369-01286523369-01286560892-01286569024- --> +<LI><A HREF="001044.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1044"> </A> +<I>Renaud MICHEL +</I> + +<!--3 01286495369-01286523369-01286560892-01286569024-01286570073- --> +<LI><A HREF="001046.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1046"> </A> +<I>Frank Griffin +</I> + +</UL> +</UL> +</UL> +<!--0 01286512217- --> +<LI><A HREF="001023.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1023"> </A> +<I>Fernando Parra +</I> + +<!--0 01286530160- --> +<LI><A HREF="001025.html">[Mageia-dev] test +</A><A NAME="1025"> </A> +<I>Angelo Naselli +</I> + +<!--0 01286545598- --> +<LI><A HREF="001027.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1027"> </A> +<I>Florian Hubold +</I> + +<UL> +<!--1 01286545598-01286546876- --> +<LI><A HREF="001029.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1029"> </A> +<I>Gustavo Giampaoli +</I> + +<!--1 01286545598-01286564658- --> +<LI><A HREF="001039.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1039"> </A> +<I>Tux99 +</I> + +<UL> +<!--2 01286545598-01286564658-01286566354- --> +<LI><A HREF="001040.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1040"> </A> +<I>Marc Paré +</I> + +</UL> +<!--1 01286545598-01286567097- --> +<LI><A HREF="001041.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1041"> </A> +<I>Marc Paré +</I> + +<!--1 01286545598-01286570891- --> +<LI><A HREF="001047.html">[Mageia-dev] What do you think about create a Mageia Welcome Center? +</A><A NAME="1047"> </A> +<I>David W. Hodgins +</I> + +</UL> +<!--0 01286545965- --> +<LI><A HREF="001028.html">[Mageia-dev] Talk of Browsers +</A><A NAME="1028"> </A> +<I>Florian Hubold +</I> + +<!--0 01286549668- --> +<LI><A HREF="001030.html">[Mageia-dev] A new office suite ? +</A><A NAME="1030"> </A> +<I>Florian Hubold +</I> + +<!--0 01286551842- --> +<LI><A HREF="001031.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1031"> </A> +<I>andré +</I> + +<UL> +<!--1 01286551842-01286558189- --> +<LI><A HREF="001034.html">[Mageia-dev] How will be the realese cycle? +</A><A NAME="1034"> </A> +<I>Buchan Milne +</I> + +</UL> +<!--0 01286562455- --> +<LI><A HREF="001035.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1035"> </A> +<I>Cassian Braconnnier +</I> + +<UL> +<!--1 01286562455-01286562934- --> +<LI><A HREF="001036.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1036"> </A> +<I>Cassian Braconnnier +</I> + +<!--1 01286562455-01286563247- --> +<LI><A HREF="001037.html">[Mageia-dev] [Mageia] Will Mageia offer MeeGo ? +</A><A NAME="1037"> </A> +<I>Thomas Canniot +</I> + +</UL> + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Fri Oct 8 22:49:01 CEST 2010</i><br> + <b>Archived on:</b> <i>Fri Oct 8 22:49:17 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + |