On 27-Sep-09, at 2:41 PM, Bernhard Pieber wrote:

> One thing I don't like at all, though: the fact that some Monticello  
> packages are dirty after I install the .sar. With the new  
> development process I got used to the fact that only the packages I  
> work on are dirty. As an old ENVY user dirty packages make me very  
> nervous. ;-)

Good point. I guess the correct thing to do would be to test for the  
presence of external packages an only load them if necessary. I'll do  
that in the next release.

> However, I loaded OB-ExtDeps and OB-Umbrella from source.wiresong.ca/ 
> ob as you have explained on the OmniBrowser Development group. That  
> seemed to have worked. Do I have all the code from the release now?

Yes, along with some additional packages that are only necessary for  
development of OmniBrowser, particularly running the tests.

> At first I had tried only loading OB-Umbrella which did not work.  
> Wouldn't it be the best - as in least confusing - way to just load a  
> package named OmniBrowser from the repository source.wiresong.ca/ob?

Well, yes, that would certainly be less confusing. But OB is divided  
in to multiple packages for good reason. It's important to be able to  
load some of the packages but not all of them. It would be nice if the  
umbrella package were called OmniBrowser, but for historical reasons,  
a package with that name already exists. If we rename it, we loose the  
ability to merge the existing branches.

I'm sorry it wasn't immediately obvious how to set up an OmniBrowser  
development environment, but it's not actually that hard, and it will  
get easier as we refine the development and release procedures.

Colin