On Feb 25, 2009, at 2:48 PM, Luca Arzeni wrote:
> For the bug: I got the tar (0.9.1) from the web site, but I did
> never update
> it.
> I didn't use setup, and I didn't write sources in my site's dir,
> because I
> feel the need to explore them (ed eventually change them) so I keep
> them in
> my home dir, and I don't know how to use web update in this situation.
It should run automatically on startup, as long as you haven't
disabled it.
> Anyway, beside this, I don't like the idea of having (unconscious)
> changes
> to my codebase, to avoid the "Now it's working differently, but I
> didn't
> change anything!" syndrome...
Nothing is ever updated in the background. You will always be
notified of updates, and can choose not to update when you don't want
to update your system.
> Is there any way to have a list of changes from web updates, review
> them and
> applying them only after a review?
That's something that I'd love to add, but it's pretty far down on my
list of things to do. My philosophy on this is that I never push a Web
Update while we are changing things, but only after we've got the bugs
worked out. This way you're getting the latest version of the code,
with all the bug fixes and efficiency improvements, but without having
to live on the bleeding edge.
> I'm setting up a local svn server and I could use it to keep track
> of the
> patches, if it's needed.
You can always find the latest revision number in Web Update for the
framework as well as all the tools by going to:
http://dabodev.com/wiki/FAQs#LatestWebUpdateRevisionNumber
You could run svn log between that revision and your current one, or
browse the changes on Trac: http://trac.dabodev.com/log/
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
