summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-October/019683.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-October/019683.html')
-rw-r--r--zarb-ml/mageia-dev/2012-October/019683.html146
1 files changed, 146 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-October/019683.html b/zarb-ml/mageia-dev/2012-October/019683.html
new file mode 100644
index 000000000..f86be3b7c
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-October/019683.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] rehashing the faac issue
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3C50908365.3060903%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="019661.html">
+ <LINK REL="Next" HREF="019651.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] rehashing the faac issue</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20rehashing%20the%20faac%20issue&In-Reply-To=%3C50908365.3060903%40laposte.net%3E"
+ TITLE="[Mageia-dev] rehashing the faac issue">andre999mga at laposte.net
+ </A><BR>
+ <I>Wed Oct 31 02:48:21 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="019661.html">[Mageia-dev] rehashing the faac issue
+</A></li>
+ <LI>Next message: <A HREF="019651.html">[Mageia-dev] rehashing the faac issue
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19683">[ date ]</a>
+ <a href="thread.html#19683">[ thread ]</a>
+ <a href="subject.html#19683">[ subject ]</a>
+ <a href="author.html#19683">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Johnny A. Solbu a &#233;crit :
+&gt;<i> On Tuesday 30 October 2012 09:30, andre999 wrote:
+</I>&gt;&gt;&gt;<i> The problem of including nonfree spftware in tainted, is that it
+</I>&gt;&gt;&gt;<i> no longer is a Free software repo in countries that don't accept
+</I>&gt;&gt;&gt;<i> software patents.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> So how is that a problem ?
+</I>&gt;<i>
+</I>&gt;<i> I am one of those that have core and tainted activated, but not
+</I>&gt;<i> nonfree. I know that every available package urpm can find is Free
+</I>&gt;<i> and open source software. If we start to include nonfree packages in
+</I>&gt;<i> tainted, one can no longer activate tainted and be sure that every
+</I>&gt;<i> package available for instalation is Free software.
+</I>&gt;<i>
+</I>&gt;&gt;<i> Would it help if a user could set a configuration to automatically
+</I>&gt;&gt;<i> control the installation of non-free packages. Something like
+</I>&gt;&gt;<i> &quot;never&quot;, &quot;confirm each time&quot;, or &quot;always&quot;, similar to what has been
+</I>&gt;&gt;<i> proposed for isos ?
+</I>&gt;<i>
+</I>&gt;<i> If it also works with urpm in the terminal, yes it's a help. I never
+</I>&gt;<i> use the graphical package management tools to install anything,
+</I>&gt;<i> unless I'm showing a user how to use the system. The only time I open
+</I>&gt;<i> the graphical package manager, is to browse through the categories
+</I>&gt;<i> just to see what's there. Sometimes i find cool games this way.
+</I>
+Myself I prefer graphic tools when they accomplish my goal more readily,
+which is most of the time installing packages. Fewer problems with typos.
+&gt;<i>
+</I>&gt;<i> The &#171;never&#187; option should work with the terminal tools like urpmq and
+</I>&gt;<i> urpmf. Meaning, if one choose to configure it to ignore nonfree
+</I>&gt;<i> packages, it should also not show up in searches. Which is one of the
+</I>&gt;<i> benefits of having separate repos.
+</I>
+My idea is to store such a configution option in the global section (at
+the beginning) of /etc/urpmi/urpmi.cfg, so it would be available to both
+console and graphic tools.
+
+&gt;<i>
+</I>&gt;&gt;<i> Don't forget that packages in the tainted repo have to be
+</I>&gt;&gt;<i> downloaded from the net, unlike packages in core or nonfree, which
+</I>&gt;&gt;<i> could be on an iso.
+</I>&gt;<i>
+</I>&gt;<i> That depends. I never install from anything else but a network
+</I>&gt;<i> install. Mainly because i have access to much more software in one
+</I>&gt;<i> go. In the cases I install from a DVD iso it is on behalf of another
+</I>&gt;<i> user, and I usually add a repo anyway. In the past when I installed
+</I>&gt;<i> from a DVD on my own systems, I always added my local repo mirror.
+</I>&gt;<i> (urpmi.addmedia --distrib blahblah)
+</I>
+I was thinking of internet installs -- which are often unreliable (at my
+location), if installing/updating many packages. (It seems to depend on
+the weather, even though I have a wired connexion to internet.)
+
+&gt;<i>
+</I>&gt;&gt;<i> So having an additional control, and using the &quot;never&quot; option would
+</I>&gt;&gt;<i> eliminate any chance of installing a non-free package from
+</I>&gt;&gt;<i> tainted.
+</I>&gt;<i>
+</I>&gt;<i> As would a new repo. :-)=
+</I>&gt;<i>
+</I>&gt;&gt;<i> Wouldn't that work for you ?
+</I>&gt;<i>
+</I>&gt;<i> Yes, for me that would work, but this is not my point. :-)= I'm not
+</I>&gt;<i> making noice because it's an inconvenience to Me, but because if we
+</I>&gt;<i> do this we are thowing out our long standing tradition of separating
+</I>&gt;<i> Free software from Nonfree software.
+</I>&gt;<i>
+</I>If I'm not mistaken, constrained packages tend to be presented elsewhere
+in a single set of repos, free and non-free together.
+I do agree that the category should be very clearly identified.
+As it stands now, most non-free and many constrained(tainted) packages
+have nothing in their name to indicate their category. So if a package
+is not in the correct repo, there is no easy means to determine its'
+category. If we require a tag the package name for all non-free, and
+similarly for all tainted, we would loose this ambiguity.
+Note that if urpmi is configured to keep downloaded packages after
+install, all packages, whatever their category, whatever release, are
+put in the same directory. Putting a tag in the name would remove the
+resulting ambiguity.
+
+Besides the extra overhead, the thought of another set of repos with a
+configuration to maintain is not inviting.
+It wouldn't be so bad if configuration were presented in a grid instead
+of an endless list, at least for official repos.
+If the presentation were simplified and a way found to minimise any
+overhead, I'm not necessarily against an extra set of repos. But having
+to scroll down a few pages to review the configuration, or select among
+a dozen repos every time one updates, is a pain.
+
+--
+Andr&#233;
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="019661.html">[Mageia-dev] rehashing the faac issue
+</A></li>
+ <LI>Next message: <A HREF="019651.html">[Mageia-dev] rehashing the faac issue
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#19683">[ date ]</a>
+ <a href="thread.html#19683">[ thread ]</a>
+ <a href="subject.html#19683">[ subject ]</a>
+ <a href="author.html#19683">[ 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>