1 |
On Tue, Jan 03, 2012 at 08:12:06PM +0100, Fabian Groffen wrote: |
2 |
> > I think the best way to do this part of it is going to be to just follow |
3 |
> > the upstream packages. When they release a new version that installs in |
4 |
> > /usr, just allow that to happen. Eventually there will be very little in |
5 |
> > /{bin,sbin,lib}, maybe nothing besides a couple of symbolic links like |
6 |
> > /bin/sh. |
7 |
> |
8 |
> What packages would that be? If you're thinking about coreutils, just |
9 |
> trim down the ebuild by not moving some of the tools to /bin. Our |
10 |
> ebuild makes it conform to FHS, not the coreutils buildsystem itself. |
11 |
|
12 |
Yes, coreutils will have to be reworked in that case. I don't know what |
13 |
the upstream build system does, but we will have to take a look at it. |
14 |
|
15 |
I'll have to go through on my system at |
16 |
least and find all of the ebuilds that install things in |
17 |
/{bin,sbin,lib}. I'll open a tracker bug as soon as udev-176 is |
18 |
released; this will list all of the things we need to do to complete the |
19 |
migration. |
20 |
|
21 |
Basically I have these in my head: |
22 |
|
23 |
* mask udev-176 in the tree. |
24 |
* figure out and document how to make a simple initramfs with dracut. |
25 |
* unmask udev 176 making sure to point users with a separate /usr |
26 |
partition to how to make an initramfs (I could probably do this with |
27 |
ewarns in the ebuild and maybe a news item before we go stable). |
28 |
* stabilize a version of dracut. |
29 |
* stabilize >=udev-176 and kmod. |
30 |
* Now start stabilizing packages with things installed in /usr instead |
31 |
of /. |
32 |
|
33 |
If you do not have separate /usr, you could just enjoy the ride. All |
34 |
of this would be transparent to you. If you do have separate /usr, the |
35 |
critical step will be bringing up an initramfs once you upgrade to |
36 |
udev-176. Once that is done, you could also just enjoy the ride. |
37 |
|
38 |
Thoughts? |
39 |
|
40 |
William |