The other thing I thought about while I was a way:
- Perhaps we could make a dir trunk/accessibility
Which could contain all accessibility diffs that developers aren't so
sure about eg. more menu items, or big voice files. And that way the
diffs would be kept up-to-date in svn...
So then all a blind user would have to do is apply
trunk/accessibility/*
to their build instead of searching the tracker for many patches and
dealing with dependencies...
We could also write docs and put them in that dir that list the
dependencies, a description of the patch and the order that they should
be applied. Also we could put an all.diff patch there for everything...
I can see your point it would save a lot of patch hunting.
However, it wouldn't stop patches going out of sync with current svn as they
wouldn't be kept up to date to work with current code. As if this was an
optional folder that wasn't applied normally to svn developers wouldn't take
account of it when making changes to the main svn.
