1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
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 écrit :
><i> On Tuesday 30 October 2012 09:30, andre999 wrote:
</I>>>><i> The problem of including nonfree spftware in tainted, is that it
</I>>>><i> no longer is a Free software repo in countries that don't accept
</I>>>><i> software patents.
</I>>><i>
</I>>><i> So how is that a problem ?
</I>><i>
</I>><i> I am one of those that have core and tainted activated, but not
</I>><i> nonfree. I know that every available package urpm can find is Free
</I>><i> and open source software. If we start to include nonfree packages in
</I>><i> tainted, one can no longer activate tainted and be sure that every
</I>><i> package available for instalation is Free software.
</I>><i>
</I>>><i> Would it help if a user could set a configuration to automatically
</I>>><i> control the installation of non-free packages. Something like
</I>>><i> "never", "confirm each time", or "always", similar to what has been
</I>>><i> proposed for isos ?
</I>><i>
</I>><i> If it also works with urpm in the terminal, yes it's a help. I never
</I>><i> use the graphical package management tools to install anything,
</I>><i> unless I'm showing a user how to use the system. The only time I open
</I>><i> the graphical package manager, is to browse through the categories
</I>><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.
><i>
</I>><i> The «never» option should work with the terminal tools like urpmq and
</I>><i> urpmf. Meaning, if one choose to configure it to ignore nonfree
</I>><i> packages, it should also not show up in searches. Which is one of the
</I>><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.
><i>
</I>>><i> Don't forget that packages in the tainted repo have to be
</I>>><i> downloaded from the net, unlike packages in core or nonfree, which
</I>>><i> could be on an iso.
</I>><i>
</I>><i> That depends. I never install from anything else but a network
</I>><i> install. Mainly because i have access to much more software in one
</I>><i> go. In the cases I install from a DVD iso it is on behalf of another
</I>><i> user, and I usually add a repo anyway. In the past when I installed
</I>><i> from a DVD on my own systems, I always added my local repo mirror.
</I>><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.)
><i>
</I>>><i> So having an additional control, and using the "never" option would
</I>>><i> eliminate any chance of installing a non-free package from
</I>>><i> tainted.
</I>><i>
</I>><i> As would a new repo. :-)=
</I>><i>
</I>>><i> Wouldn't that work for you ?
</I>><i>
</I>><i> Yes, for me that would work, but this is not my point. :-)= I'm not
</I>><i> making noice because it's an inconvenience to Me, but because if we
</I>><i> do this we are thowing out our long standing tradition of separating
</I>><i> Free software from Nonfree software.
</I>><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é
</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>
|
