| Update procedure needs documentation [message #568639] |
Tue, 10 June 2008 17:29 |
 John J. Barton
Messages: 311
Registered: July 2009 |
Senior Member |
|
|
Thanks to Eric Rizzo I found out where the PDE newsgroup is hiding.
Here I am offering two kinds of feedback to the PDE team:
1) As a long time PDE user I have tried the update site thing several
times in the past. I never succeeded. When I asked around to get help,
every time the response was laughter, rolling of eyes, etc. followed by
suggestions involving workarounds or "yea I got it to work after three
or four days but I don't know why".
Last week I really needed an update site solution. I worked at it for
several days. Then I got it work, I don't know why.
Ok, so I'm an idiot and work with same, but it seems to me that this
powerful tool is very difficult for first time use.
2) I was not able to find any documentation on what a developer should
do to cause updates to be seen by the user. I thought it would be
completely obvious: a new update would be created every time I went to
the ** update site ** project and pushed "build all". What else could
that operation mean? After a lot of trial and error I found out that
this procedure works:
1) Manually update the version number on you plugin.
2) Manually update the version number on your feature.
3) Add the new feature version to update site
4) Build all.
Seems like this is too complicated, but at least the docs should give
the procedure.
John.
|
|
|
Powered by
FUDForum. Page generated in 0.03304 seconds
] 
Search
Help
Register
Login
Home
