1 |
>>>>> On Tue, 3 Nov 2009, Ciaran McCreesh wrote: |
2 |
|
3 |
> Due to insufficient clarity in the proposal, the PMS team hasn't |
4 |
> been able to come up with a wording that wouldn't either require |
5 |
> changes to Portage (which appears to be against the Council's |
6 |
> intent) or that would permit behaviour currently seen as |
7 |
> undesirable. As I understand it, the issues are: |
8 |
|
9 |
> * What's to be done about sub-second timestamps? What about cases |
10 |
> where the build filesystem supports them but the root filesystem |
11 |
> doesn't? |
12 |
|
13 |
Obviously we cannot guarantee anything below the seconds level because |
14 |
of limitations in the underlying filesystems or software (e.g., tar |
15 |
for binpkgs). But is there a reason for limiting it further, i.e. not |
16 |
preserving sub-second timestamps if they are supported by both |
17 |
filesystems? |
18 |
|
19 |
> * For which files must mtimes be preserved, and which can be modified? |
20 |
|
21 |
> * Is it the intent of this proposal to prevent package managers from |
22 |
> automatically rewriting, say, #!/usr/bin/python to |
23 |
> #!/opt/gentoo/bin/python if prefix is being used? |
24 |
|
25 |
Part of the problem (what you call "insufficient clarity") is that the |
26 |
proposal's original intention was to cover only the merge process, |
27 |
i.e. what takes place after pkg_preinst. Whereas you want to extend it |
28 |
to include everything that is taking place after src_install (for |
29 |
Portage, prepstrip and whatnot). |
30 |
|
31 |
If you limit it to the final merge process from D to ROOT, then the |
32 |
answer is easy, namely mtimes of all regular files must be preserved. |
33 |
|
34 |
Ulrich |