svn:externals not correctly displayed in browser

[anonymous]

Using Trac 0.11b1, svn:externals can be followed using the browser.

However, imagine a directory which only contains links to externals modules (this could be a common use case, putting all external stuff in one place). Then when clicking on the left arrow to expand this folder, the "jquery Loading..." sends back an (empty) directory ! This is correct from a subversion point of view but a bit strange from a user point of view (which is not supposed to know svn internals) and we have to click on the directory name to get the svn:external link displayed.

The proposal should be : creating a particular directory entry icon which could represent an external link. Then, this link would be displayed as a special directory entry and the user would be able to follow this link without being disturbed by an empty dir content.

I put here another thougth as it is linked to my previous description : A great improvement of the svn:externals functionality would be to follow the link within the trac browser if the link target is related to the same repos. Indeed, consider this situation :

• Repos is stored here http://myserver/svn/repos
• The source directoy is http://myserver/svn/repos/project1/
• the target directory is http://myserver/svn/repos/modules/module1

The svn:externals property of http://myserver/svn/repos/project1/ is set to "module1 http://myserver/svn/repos/modules/module1"
Then when following the link in the trac browser http://myserver/trac/browser/project1/module1 , we are redirected to http://myserver/svn/repos/modules/module1 which is correct but which leaves trac pages. As the link is "external" from a svn point of view but "internal" from a trac point of view, the address could be transformed on the fly to http://myserver/trac/browser/modules/module1

[eblot]

Should not block 0.11 release.

[cboos]

Complementary to #6474

(and I start to be a bit more realistic for the planning of cool but non essential features ;-) )

[osimons]

Also, this pre-supposes some knowledge of the URL location of the repos hooked onto Trac - see #1781 for discussion on that. Currently Trac only knows the path on disk.