[wp-hackers] Plugin zip problem on wordpress.org

Moritz 'Morty' Strübe morty at gmx.net
Wed Nov 14 09:20:37 GMT 2007


Michael D Adams schrieb:
>>> Zip files from other tags (downloaded from the "other versions" link,
>>> e.g. http://wordpress.org/extend/plugins/podpress/download/) will
>>> contain the *entire* SVN tree.  Why?  We determine the "packaging
>>> subdirectory" from the readme file in trunk/.  The directory structure
>>> can change between tags, so we can't know from trunk/readme.txt what
>>> the right thing to do is for any tag but the stable one.  We could
>>> parse each tag's readme.txt, but I'm not convinced that's useful for
>>> plugin authors or users.  This is *inconsistent*.  Is that bad?
>>
>> Looking at this more closely makes things more difficult, indeed. How
>> about adding an option instead of enhancing one.
>>
>> Stable Tag: 2.1
>> Release Path: release
>>
>> So where is the advantage? The inconsistency will be solved. "Release
>> Path" is read from the directory that is packed. This would even work
>> for older versions, changing the readme.txt in your tag-dir. As long as
>> the trunk-dir-tree is the same as the tag-dir-tree there shouldn't be
>> any problems. - At least I can't see any. Of course packing everything
>> would be fall back.
>
> It's the same problem.
>
> Either we look at each tag's readme file and parse a subdirectory or a
> Release Path tag or whatever, or we just look at trunk's readme file. 
> If doing this for every tag is useful/makes more sense/is a better
> user experience, that's fine.  We just need to convince ourselves of
> that.

One shouldn't write emails late at night in a foreign language.  ;-)
The Idea was to have a "global" and a "local" option.
The global one is "Stable Tag" and always read from the trunk. This is
more or less the information where the "latest"-link should go.
Release Path is a local option. It's read from the tag that is going to
be ziped. If you have a different directory tree in your trunk and your
tag, you have to change this option in your tag after tagging. Not nice,
but at least it's possible.
Hope it makes more sense this time ;-)


>
>> P.s.: Can you change my dir-name from post-notification to
>> post_notification? - If it isn't too much trouble. Otherwise it would be
>> nice to have an option how to name the directory, too.
>
> The dir-name will always be the same as your SVN repo name:
> post-notification in your case.  That way your svn repo, the url in
> the plugin directory, the plugin zip, and the directory the plugin zip
> contains all have the same name.  I don't see any reason a plugin
> should want to or be able to change that.
>
> As an aside, WP has always used hyphens for files and urls over
> underscores.  It's what sets us apart from MT :)
Looks like I have to do some work on dir-names.... :-/

Cheers
Morty

-- 

strübe.de <http://xn--strbe-mva.de>


.



More information about the wp-hackers mailing list