1 |
On Wed, 04 Nov 2009 13:12:37 -0800 |
2 |
Zac Medico <zmedico@g.o> wrote: |
3 |
> > So far as I can see, if they're fully supported on both filesystems, |
4 |
> > Portage sometimes preserves nanosecond-resolution timestamps and |
5 |
> > sometimes doesn't. So, requiring nanosecond-resolution timestamp |
6 |
> > preservation where possible will need Portage changes. |
7 |
> |
8 |
> I think it always preserves them, as long as you have at least |
9 |
> python-2.5 since that is required for floating-point mtime support. |
10 |
|
11 |
Mm, I can't see the code for that. So far as I can see, for the |
12 |
non-fast case you're using stat.st_mtime and os.utime, which assuming |
13 |
they correspond to the POSIX things of the same name, are |
14 |
second-resolution. What am I missing? |
15 |
|
16 |
-- |
17 |
Ciaran McCreesh |