On 24 May 2009, at 18:45, Carlo de Falco wrote:
On 17 May 2009, at 22:40, Søren Hauberg wrote:
søn, 17 05 2009 kl. 22:34 +0200, skrev Carlo de Falco:
If we change
generate_package_html (..., ..., "octave-forge")
to produce one file for each package containing the text that is
meant
to
On 17 May 2009, at 22:40, Søren Hauberg wrote:
søn, 17 05 2009 kl. 22:34 +0200, skrev Carlo de Falco:
If we change
generate_package_html (..., ..., "octave-forge")
to produce one file for each package containing the text that is
meant
to go on that page,
then the server-side script would
søn, 17 05 2009 kl. 22:34 +0200, skrev Carlo de Falco:
> If we change
>
> generate_package_html (..., ..., "octave-forge")
>
> to produce one file for each package containing the text that is meant
> to go on that page,
> then the server-side script would just need to read all files in a
> gi
On 17 May 2009, at 22:22, Søren Hauberg wrote:
> Will this be fast enough? The page
>
> http://octave.sourceforge.net/packages.html
>
> contains the list of packages. Notice that it includes descriptions of
> each package. If this should be generated on the fly we would need to
> read some file
søn, 17 05 2009 kl. 22:14 +0200, skrev Carlo de Falco:
> On 17 May 2009, at 15:41, Søren Hauberg wrote:
>
> >
> > The tricky part about the unsolved problems is that they should be
> > easy
> > to work with when we have many people doing releases rather than only
> > one person. My current idea
On 17 May 2009, at 15:41, Søren Hauberg wrote:
>
> The tricky part about the unsolved problems is that they should be
> easy
> to work with when we have many people doing releases rather than only
> one person. My current idea is to have some python/perl/whatever
> script
> on the web server
søn, 17 05 2009 kl. 15:16 +0200, skrev Rafael Laboissiere:
> * Søren Hauberg [2009-05-17 14:44]:
>
> > I could manually create the package and put that online. I've been
> > thinking about re-releasing a few packages ('communications' and 'nnet')
> > since they contain bugs that prevent them from
* Søren Hauberg [2009-05-17 14:44]:
> I could manually create the package and put that online. I've been
> thinking about re-releasing a few packages ('communications' and 'nnet')
> since they contain bugs that prevent them from actually installing. So,
> I guess I could make a manual release of
søn, 17 05 2009 kl. 14:32 +0200, skrev Rafael Laboissiere:
> There is a problem with the downloading of the fenv package from
> SourceForge. The URL link [1] present in the fenv pkg page [2] is
> broken. Indeed, fenv is absent from the R2009-05-09 release of the Octave
> Forge packages [3]. Can t
There is a problem with the downloading of the fenv package from
SourceForge. The URL link [1] present in the fenv pkg page [2] is
broken. Indeed, fenv is absent from the R2009-05-09 release of the Octave
Forge packages [3]. Can this be fixed, please?
[1] http://downloads.sourceforge.net/octave/
10 matches
Mail list logo
