[sldev] Packaging the viewer for Linux distributions

[John Hurliman]

Dale Glass wrote:
> On Friday 05 October 2007 23:43:16 Callum Lerwick wrote:
>   
>> LL already separates the "artwork" from the viewer source, which is most
>> of the way there. What makes it much less useful to us is the fact that
>> a new artwork tarball comes out with every source release. Could LL
>> avoid releasing a new artwork tarball unless it has actually changed? I
>> haven't got around to diffing it and seeing how often it actually
>> changes, if it is changing, maybe it shouldn't. ;P
>>     
>
> How about putting the artwork and libraries packages into SVN (or 
> whatever)? That'd allow to tell much more easily when it changes, and 
> updates would be less of a pain.
>   
>
>   


The openmetaverse.org project went the route of putting everything in 
SVN, and branching can be a huge pain. Having 10,000(ish) boost header 
files in every single branch and tag creates these monstrous databases 
and makes committing and checking out a huge pain every time a new 
release is made. In theory I would love to see everything in SVN, but we 
found out in practice it can be fairly painful.

Also, one odd thing I noticed is it seems to be easier at LL to get 
stuff in the artwork or libraries packages then in to SVN. The MSVC 2005 
project files in SVN are more or less the originals I submitted long 
long ago on a JIRA task and haven't been updated in ages, yet the 
libraries package comes with (almost) updated solution/project files 
that overwrite the ones in SVN! I would hate to see this "easy" avenue 
of pushing out bleeding edge stuff to the community squashed.

John Hurliman