Bugzilla – Full Text Bug Listing
| Summary: | Allow symlinks on download.eclipse.org | ||
|---|---|---|---|
| Product: | Community | Reporter: | Markus Kuppe <bugs.eclipse.org> |
| Component: | Website | Assignee: | phoenix.ui <phoenix.ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | gunnar |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Kuppe
Symlinks are disabled for security reasons. Also, if they were allowed on download.eclipse.org, there would be no guarantee that they would work on all our mirror sites. Your p2 repos are set up to use mirror sites, right? So providing a .../latest/ link essentially means we have to keep a duplicate of the latest ECF release on download.eclipse.org? Why a duplicate? You can put your latest release in a directory called "latest", then move it to another directory when it's no longer the latest. (In reply to comment #3) > Why a duplicate? You can put your latest release in a directory called > "latest", then move it to another directory when it's no longer the latest. To serve consumers that want to use a permanent URL for a stable release from the start (e.g. .../ecf/3.4). If it's just for p2 you should look at composite repositories. That's how you can manage a "latest" repository at a stable URL. http://wiki.eclipse.org/Equinox/p2/Composite_Repositories_(new) You should also specify a p2.mirrorsURL in your p2 repository artifacts.xml. It can be done automatically when mirroring to the final location. http://dev.eclipse.org/viewcvs/viewvc.cgi/e4/releng/org.eclipse.e4.sdk/builder/templates/artifacts.xml?revision=1.1&view=markup > Symlinks are disabled for security reasons. Also, if they were allowed on
> download.eclipse.org, there would be no guarantee that they would work on all
> our mirror sites.
I can't enable symlinks for these two reasons. Sorry.
|