summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011299.html
blob: 56d33de918e79d3ac8212f32c2523ef024a5adcb (plain)
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
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Over-zealous rpmlint policy (rejecting rt)
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Over-zealous%20rpmlint%20policy%20%28rejecting%20rt%29&In-Reply-To=%3C1326396511.17888.25.camel%40localhost%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="011281.html">
   <LINK REL="Next"  HREF="011404.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Over-zealous rpmlint policy (rejecting rt)</H1>
    <B>Michael Scherer</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Over-zealous%20rpmlint%20policy%20%28rejecting%20rt%29&In-Reply-To=%3C1326396511.17888.25.camel%40localhost%3E"
       TITLE="[Mageia-dev] Over-zealous rpmlint policy (rejecting rt)">misc at zarb.org
       </A><BR>
    <I>Thu Jan 12 20:28:31 CET 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="011281.html">[Mageia-dev] Over-zealous rpmlint policy (rejecting rt)
</A></li>
        <LI>Next message: <A HREF="011404.html">[Mageia-dev] Over-zealous rpmlint policy (rejecting rt)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#11299">[ date ]</a>
              <a href="thread.html#11299">[ thread ]</a>
              <a href="subject.html#11299">[ subject ]</a>
              <a href="author.html#11299">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le jeudi 12 janvier 2012 &#224; 11:12 +0200, Buchan Milne a &#233;crit :
&gt;<i> I am trying to get rt (3.8.11) into the distro (a package that I am using on a 
</I>&gt;<i> different distro in a production environment), to be followed up with the rt 
</I>&gt;<i> (4.0.4) I have queued (which I am testing in preparation for upgrading our 
</I>&gt;<i> production environment).
</I>&gt;<i> 
</I>&gt;<i> I would really like to get this package into the distro, but it is being 
</I>&gt;<i> rejected 
</I>&gt;<i> (<A HREF="http://pkgsubmit.mageia.org/uploads/rejected//cauldron/core/release/20120110140334.buchan.valstar.18287.youri">http://pkgsubmit.mageia.org/uploads/rejected//cauldron/core/release/20120110140334.buchan.valstar.18287.youri</A>) 
</I>&gt;<i> due to:
</I>&gt;<i> 
</I>&gt;<i> Submission errors, aborting:
</I>&gt;<i> - rt-3.8.11-1.mga2.noarch:
</I>&gt;<i>  - dir-or-file-in-usr-local /usr/local/lib/rt/plugins
</I>&gt;<i>  - dir-or-file-in-usr-local /usr/local/lib/rt
</I>&gt;<i>  - dir-or-file-in-usr-local /usr/local/lib/rt/po
</I>&gt;<i>  - dir-or-file-in-usr-local /usr/local/lib/rt/lib
</I>&gt;<i>  - dir-or-file-in-usr-local /usr/local/etc/rt
</I>&gt;<i>  - dir-or-file-in-usr-local /usr/local/lib/rt/html
</I>&gt;<i> 
</I>&gt;<i> The documented way for extending RT is by installing files in this location. 
</I>&gt;<i> We can either:
</I>&gt;<i> 1)Make it more difficult for users to extend RT with local plugins etc.
</I>&gt;<i> 2)Fix rpmlint
</I>&gt;<i> 3)Not have RT
</I>&gt;<i> 
</I>&gt;<i> misc, you have experience of both rt and rpmlint, can you provide an opinion?
</I>&gt;<i>
</I>&gt;<i> Would it be possible to separate 'dir-or-file-usr-local' into separate rules 
</I>&gt;<i> (one for files, one for dirs)? While I agree we shouldn't ship files in 
</I>&gt;<i> /usr/local, I don't see why we shouldn't ship dirs in /usr/local ...
</I>
We shouldn't ship directories for the same reason that we shouldn't ship
file, ie FHS.

See :
<A HREF="http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#USRLOCALLOCALHIERARCHY">http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#USRLOCALLOCALHIERARCHY</A>

More specifically :
&quot;It needs to be safe from being overwritten when the system software is
updated.&quot;

So the question is whether someone who change directory permissions will
see them overwritten or not when the software is updated, and wether
that a FHS violation.

Afaik, rpm would reset the permission ( the same goes for removal of the
directory ). 

See also :
&quot;No other directories, except those listed below, may be in /usr/local
after first installing a FHS-compliant system.&quot;

Again, that's not clear if we can modify it later or not ( ie, is
instaling rt on installation part of &quot;first installing&quot; or not ).

I guess we should get a opinion from FHS/LSB people on this.

In the mean time, I guess the point 1 is the easiest way, it can be
changed later once we clarified FHS (or if we decide that we do not care
about following standards, but that's really something I would like to
avoid ). 

-- 
Michael Scherer

</PRE>









































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="011281.html">[Mageia-dev] Over-zealous rpmlint policy (rejecting rt)
</A></li>
	<LI>Next message: <A HREF="011404.html">[Mageia-dev] Over-zealous rpmlint policy (rejecting rt)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#11299">[ date ]</a>
              <a href="thread.html#11299">[ thread ]</a>
              <a href="subject.html#11299">[ subject ]</a>
              <a href="author.html#11299">[ 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>