[chirp_users] How to install Development builds

chirp.fratermus at spamgourmet.net chirp.fratermus at spamgourmet.net
Fri Jul 27 06:32:18 PDT 2012


> From: "Jay Moran, N2JCM" <jay+CHIRP at tp.org>
> Subject: Re: [chirp_users] How to install Development builds

> http://trac.chirp.danplanet.com/chirp_daily/
>
> >From there you can scan through looking for the latest daily build date, as
> of today that would be daily-20120724. Here is a direct link:
...
> Of course, that date/link will change when there is a new build available.

Does anyone else see any value in symlinks on the server that would
point to the latest directory/builds?  IMO it could simplify project
documentation and would simplify scripting solutions to pull the the
latest version programmatically on non-*buntu platforms.

The most recent example would be:
daily-latest/ --> daily-20120724/
chirp-daily-latest-installer.exe --> chirp-daily-20120724-installer.exe
chirp-daily-latest-win32.zip --> chirp-daily-20120724-win32.zip
chirp-daily-latest.app.zip --> chirp-daily-20120724.app.zip
chirp-daily-latest.tar.gz --> chirp-daily-20120724.tar.gz

Under this model this kind of URL would always be valid:
http://trac.chirp.danplanet.com/chirp_daily/daily-latest/chirp-daily-latest-win32.zip

This all assumes the dailies are published by a script that would be
amenable to automagically updating the symlinks (delete the current
links and make new ones to the new dailies).  If it's done by hand
then return on invested effort would be much less.



-- 
Jason Carr
http://www.mousetrap.net/mouse/




More information about the chirp_users mailing list