zarb-ml/mageia-dev/2012-July/017268.html


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Planning the /usr move
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Planning%20the%20/usr%20move&In-Reply-To=%3C20120711123904.GB15648%40bkor.dhs.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="017266.html">
   <LINK REL="Next"  HREF="017269.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Planning the /usr move</H1>
    <B>Olav Vitters</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Planning%20the%20/usr%20move&In-Reply-To=%3C20120711123904.GB15648%40bkor.dhs.org%3E"
       TITLE="[Mageia-dev] Planning the /usr move">olav at vitters.nl
       </A><BR>
    <I>Wed Jul 11 14:39:04 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="017266.html">[Mageia-dev] Planning the /usr move
</A></li>
        <LI>Next message: <A HREF="017269.html">[Mageia-dev] Planning the /usr move
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#17268">[ date ]</a>
              <a href="thread.html#17268">[ thread ]</a>
              <a href="subject.html#17268">[ subject ]</a>
              <a href="author.html#17268">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Wed, Jul 11, 2012 at 12:52:17PM +0100, Colin Guthrie wrote:
&gt;<i>  2. Add a patch to RPM that introduces a new check that must pass before
</I>&gt;<i> a given RPM can be installed.
</I>&gt;<i>  3. Create a new &quot;filesystem&quot; build that uses this check.
</I>[..]
&gt;<i> Several other packages will be subsequently broken (some packages ship
</I>&gt;<i> their binaries in /bin but symlink them to /usr/bin  but when /bin is
</I>&gt;<i> itself a symlink to /usr/bin, they package ultimately conflicts with
</I>&gt;<i> itself!). We need to identify such packages and fix them and have them
</I>&gt;<i> ready to go. In order to do the transition correctly, we may need to fix
</I>&gt;<i> them first, build them and then wait until all such packages are fixed,
</I>&gt;<i> THEN update the filesystem rpm and then rebuild all such packages with a
</I>&gt;<i> dep on the filesystem &gt; x package. This might be needed to avoid any
</I>&gt;<i> problems on the build system chroots.
</I>
Shouldn't those packages also rely on the new RPM check? Or you mean
just update those packages and don't allow for symlinks between /bin and
/usr/bin (+same for sbin)?

Would the new RPM do a runtime check to see if things have been
migrated?

Does Dracut usrmove handle the packages which at the moment contain
symlinks (e.g. /bin/foo -&gt; /usr/bin/foo and e.g. /usr/bin/bar -&gt;
/bin/bar)? Or should either dracut or the packages have conflicts to
deal with this?

-- 
Regards,
Olav
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="017266.html">[Mageia-dev] Planning the /usr move
</A></li>
	<LI>Next message: <A HREF="017269.html">[Mageia-dev] Planning the /usr move
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#17268">[ date ]</a>
              <a href="thread.html#17268">[ thread ]</a>
              <a href="subject.html#17268">[ subject ]</a>
              <a href="author.html#17268">[ 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>