Summary: | mtime issues with softlinks in stage tarballs | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Torsten Veller (RETIRED) <tove> |
Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Torsten Veller (RETIRED)
2006-04-19 08:22:39 UTC
Have a suggested fix? Like I said, unless there's a tar option to tell it to preserve those mtimes at creation, there's nothing I can do about it. Reassigning to catalyst since this is a catalyst issue. Sorry, I don't have a fix. But i think we need to fix this. I guess there is no option for tar. I found: | The reason is that there's no Unix system call that tar could use to set | the time of a symlink. The utime() syscall follows links. (from <http://groups.google.com/group/comp.unix.programmer/msg/3b8e9ba28bc188bd>) It doesn't sound like it is something that we *can* fix. Since all of our release materials use portage, the only "fix" for this is to change portage behavior. There's nothing I can do to fix this on the release side of things, either manually, or via catalyst. Basically, there's nothign I can do about it. |