1 |
On Sun, Aug 18, 2013 at 10:48 PM, William Hubbs <williamh@g.o> wrote: |
2 |
> Basically the status quo includes specific changes that were made in |
3 |
> our packaging to allow this sort of working separate /usr without |
4 |
> initramfs configuration to continue limping along, but we need to undo |
5 |
> them. |
6 |
|
7 |
Why do we have to undo them? |
8 |
|
9 |
I can understand that implementing them was a waste of time, but that |
10 |
time is already wasted. Does it take much effort to maintain the |
11 |
fixes? For all I know they do - but could you articulate this? |
12 |
|
13 |
I fully support that we should stop doing any more work to keep a |
14 |
separate /usr working without an initramfs. My question is why do we |
15 |
need to start undoing the work that has already been done? |
16 |
|
17 |
If you can point to some package where everytime upstream does a bump |
18 |
you have to redo 47 patches to keep it working in / but it would just |
19 |
work effortlessly if it were in /usr, that would be a great argument |
20 |
to move it back to /usr on the next bump. Maybe there is something |
21 |
else which is causing you to waste time. |
22 |
|
23 |
I'd just like to hear a driver for reverting the work that was already |
24 |
done. I fully get the argument that the work shouldn't have been |
25 |
required in the first place. What I don't get is now that the effort |
26 |
is sunk why it needs to be ditched. I think many would like to |
27 |
understand the drivers here. |
28 |
|
29 |
Otherwise it seems to me like the best path forward is to stop making |
30 |
new fixes, but just hang onto the ones we have until they no longer |
31 |
work. At some point upstream will make a change that forces our hand, |
32 |
but why not wait until then? What does it cost us to wait? |
33 |
|
34 |
Rich |