svn:externals ignored by WordPress.org plugin packager

[DD32]

It appears that svn:externals properties are ignored by the plugin packager, At least for ​svn:// urls.

Eg: ​http://svn.wp-plugins.org/revision-control/trunk (While the web interface doesnt display it, It does have a svn external property if you do a checkout) compared to ​http://downloads.wordpress.org/plugin/revision-control.zip which lacks the 'inc' folder (which is a svn:externals to ​svn://dd32.id.au/wp-plugin-dd32-common-class/)

I'm pretty sure i've set it up correctly, But it also doesnt show on ​http://plugins.trac.wordpress.org/browser/revision-control/trunk the same as it does for ​http://trac.wordpress.org/browser/trunk/wp-content/plugins with the externals, Although i think that might be a Trac setting and completely separate from the problem..

[DD32]

Just a quick update;

Setting it to ​http://svn.dd32.id.au/wp-plugin-dd32-common-class/ indeed shows it in the Trac Browser as expected, But it still doesnt end up in the zip packages.

Is it a condition whereby only wordpress.org externals are included? Or is it all externals are ignored? I've not yet checked.. It makes it hard to rely upon a helper class/code if the latest version cannot be automatically included in each plugin..

[Denis-de-Bernardy]

is this still current?

[DD32]

I'll close it when its no longer an issue.

To test if its an issue, Download ​http://downloads.wordpress.org/plugin/revision-control.zip If it contains the 'inc' folder, then This ticket can be closed, As it is, Its still being ignored.

[Denis-de-Bernardy]

it contains an inc folder.

[DD32]

it contains an inc folder.

Er... No it doesnt. SVN does, But not the .zip i linked to.. (Well.. The tagged zip's will, since i manually added them, but the trunk zip which relys on svn:externals doesnt)

[Denis-de-Bernardy]

Makes one wonder if someone is even reading the wordpress.org and maintaining the site. :D

[ryan]

I've been informed that externals are not allowed. Docs are being updated to point that out.

[strider72]

"externals are not allowed"

WHY NOT???????

[Denis-de-Bernardy]

the only reasons that would seem valid would be security and testing (scanning for function name usage for instance).

It's a shame that local externals can't be used, though. If SVN was upgraded to 1.5 or later, you can then add stuff relative to the local root:

my-lib ^/plugins/my-lib/trunk

That clearly poses no security threats. But anyway... We've learned to live without it and use our own SVN instead.