[sldev] Packaging the viewer for Linux distributions

[Argent Stonecutter]

On 10-Oct-2007, at 07:39, Robin Cornelius wrote:
> Still would need an
> installer for windows (and mac?) for first time install but nothing
> that complex is needed for an updater.

Mac doesn't need an installer, it uses the NeXTSTeP "bundle" scheme.  
GNUStep apps on other UNIX (Linux,BSD,Solaris,...) are set up the  
same way. It's really convenient... the top level directory is shown  
as a file rather than a directory in the Finder (or the old NeXTSTeP  
file manager and I assume in whatever file manager the GNUStep folks  
use), until you select "Show Contents" from the contextual menu. I'll  
go into more detail in a separate message because looking at the  
layout made me think of a couple of other comments that are kinda  
orthogonal.

> Another question, is there an easy way to check for homebrew version
> updates. I notice from the llstatup.cpp code that it running the
> update code based on a reply message to the login attempt. Great for
> official linden versions but for homebrew versions where we might have
> more releases than the lindens do with various patches being tested
> often etc, we need  a way to say there is an update available.

That was the intent of the "update-server" entry, which would be in  
something like ... the update could be checked on a schedule, or when  
the program started, and would be independent of login. You'd pull  
down the file from the <update-server> and compare the tags against  
the tags in your copy, and if they didn't match it could then do an  
rsync against the files in the <update>s.

Using rsync argument formats would allow you to specify a local file  
or a file on a local network share. You'd probably want to have  
something like <env name="RSYNC_RSH">ssh -2</env> tags or an  
rsync_cmd="env RSYNC_RSH='ssh -2' Resources/rsync -abc -xyz $1"  
attribute for special cases.