Skip to content

Setting file times on symlinks #666

@joshtriplett

Description

@joshtriplett

Proposal

Problem statement

I'd like to be able to set the file times on a symlink.

The standard library supports setting file times on an open file, using File::set_times. However, this doesn't work portably for a symlink. Changing a symlink's timestamps requires calling utimensat or lutimes depending on the system.

Motivating examples or use cases

This allows unpacking an archive with timestamps preserved, or syncing a directory between systems with timestamps preserved.

Solution sketch

// in `std::fs`
pub fn set_times_nofollow<P: AsRef<Path>>(path: P, times: FileTimes) -> Result<()>

(Modeled after std::fs::chroot and File::set_times.)

Alternatives

I'd love to implement this by opening the symlink as a file descriptor and setting the timestamp using set_times, but both steps of that are not possible in a portable way. I think this is the only reasonable approach.

What happens now?

This issue contains an API change proposal (or ACP) and is part of the libs-api team feature lifecycle. Once this issue is filed, the libs-api team will review open proposals as capability becomes available. Current response times do not have a clear estimate, but may be up to several months.

Possible responses

The libs team may respond in various different ways. First, the team will consider the problem (this doesn't require any concrete solution or alternatives to have been proposed):

  • We think this problem seems worth solving, and the standard library might be the right place to solve it.
  • We think that this probably doesn't belong in the standard library.

Second, if there's a concrete solution:

  • We think this specific solution looks roughly right, approved, you or someone else should implement this. (Further review will still happen on the subsequent implementation PR.)
  • We're not sure this is the right solution, and the alternatives or other materials don't give us enough information to be sure about that. Here are some questions we have that aren't answered, or rough ideas about alternatives we'd want to see discussed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ACP-acceptedAPI Change Proposal is accepted (seconded with no objections)T-libs-apiapi-change-proposalA proposal to add or alter unstable APIs in the standard libraries

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions