Re: update packages on octave-forge

[David Bateman]

Paul Kienzle wrote:
>
> On Jun 1, 2007, at 3:58 AM, David Bateman wrote:
>
>> What would be good is if there was a way to have a generic name on
>> the website resolve to the latest package tar-ball in the sourceforge
>> FRS. It that way the website updates could be isolated from the FRS
>> updates, and the package owner could do the uploads themselves. Any
>> ideas how to do this?
>
> The best I can think of is to run a nightly cron job that scours the
> index files of all listed packages.  This could either be via the
> web-cvs interface (brittle) or by running cvs update on a local copy
> of the repository.
>
> If any package version number has changed, it can download the package
> directory, build the tarball, and upload it via something like:
>
>     Perl -
> http://search.cpan.org/~bdfoy/Module-Release-1.16/lib/Release.pm
>    Python - http://releaseforge.sourceforge.net/
>
> It could then run the usual webpage update procedure (now build-www.py?).
>
> Because uploading requires a password, this will have to be done on a
> private machine rather than using sourceforge cron.  This same machine
> could be used as a gateway for uploading 3rd party packages.
>
> Are there any python/perl experts in the audience that can write such
> a beast and anyone willing to host such a service?
>
>     - Paul
>
>

This might be a bit fragile and end up multiplying the number of files
that are uploaded to sourceforge exponentially. A little bit of human
intervention in this process is a reasonable idea..

D.

PS. I used releaseforge for the last release and it made a job that took
4 hours for the first release, take about 30 minutes for the second
release with the update of the webpages and everything..
 

-- 
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary