| Summary: | Can we improve recommended mirrorsURL value? | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | Cross-Project | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | gunnar, john.arthorne, kim.moir, pwebster, sbouchet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
David Williams
I just use touch -t to change the timestamp on the repo directory to the time when the artifacts were first copied there and subsequently mirrored. This means when I update the compositeArtifacts and compositeContent jars to point to the child repo when the release is ready to go, but the mirrors still see the artifacts as being mirrored several days ago. From what I see, the directory timestamp only gets changed if files are added or removed, so what I do is copy, say, the artifacts.jar file to another ~/temp directory, do the unzip and editing there, jar it back up, and then copy the artifacts.jar back to its original location. This seems to not change directory timestamps, so will still be considered "mirrored". (I'm not sure this is true for ALL flavors of Linux file systems ... but, seems to work with our current one). I have added this tip to http://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL#How_to_test.3F so will consider this bug fixed. |