Ticket #8611 (closed defect (bug): wontfix)
svn:externals ignored by WordPress.org plugin packager
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | highest omg bbq | Milestone: | |
| Component: | WordPress.org site | Version: | 2.7 |
| Severity: | major | Keywords: | |
| Cc: | strider72, Denis-de-Bernardy |
Description
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..
Change History
- Cc Denis-de-Bernardy added
- Priority changed from normal to high
- Version set to 2.7
- Severity changed from normal to major
- Milestone set to 2.8
is this still current?
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.
it contains an inc folder.
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)
Makes one wonder if someone is even reading the wordpress.org and maintaining the site. :D
- Priority changed from high to highest omg bbq
- Milestone changed from 2.8 to Unassigned
comment:10
ryan — 3 years ago
- Status changed from new to closed
- Resolution set to wontfix
I've been informed that externals are not allowed. Docs are being updated to point that out.
comment:11
strider72 — 3 years ago
- Summary changed from svn:externals ignored by WordPress.org plugin packager to a good question
"externals are not allowed"
WHY NOT???????
comment:12
strider72 — 3 years ago
- Summary changed from a good question to svn:externals ignored by WordPress.org plugin packager
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.
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..