(
Jump to the original submission)
Thu 24 Nov 2016 12:35:48 AM UTC, comment #9:
The problem is still there in Octave 4.3.0+
|
Thu 16 Jun 2016 01:22:21 PM UTC, comment #8:
@Mike (comment #5)
The php scripts that you're looking for are in the project-web repository, in htdocs:
https://sourceforge.net/p/octave/project-web/ci/default/tree/htdocs/
|
Thu 16 Jun 2016 01:19:51 PM UTC, comment #7:
I meant "still takes"
|
Thu 16 Jun 2016 01:18:55 PM UTC, comment #6:
tic; pkg list -forge; toc
stills taks approximately 30 seconds on Octave 4.0.2
|
Sun 28 Jul 2013 05:10:30 PM UTC, comment #5:
I could not find any *.php scripts in the octave-forge SVN.
So the process will be you or someone else runs a script to update a hosted static file every time a new Forge package release is made?
Should the format of this file be the same as the struct saved in the local packages cache file (~/.octave_packages) so we can reuse the code that understands that structure?
|
Wed 17 Jul 2013 09:14:47 PM UTC, comment #4:
I think there's a copy of the scripts on the SVN repository.
Anyway, that has been discussed before on the mailing. It was agreed that the best solution was to have an octave struct saved in a text file and hosted in octave.org. That would have the advantage of keep working if octave forge ever moves to another server, and that be very easy for pkg to read.
|
Wed 17 Jul 2013 06:53:24 PM UTC, comment #3:
A workaround is to use
which completes much faster, but only lists the names of available packages without their versions.
A real solution to this will probably involve an improved server-side script that returns all the information needed in some structured format like XML, JSON, or even CSV. The pkg function can then get everything it needs from one URL fetch instead of tens of URLs.
Can anyone comment where are the Octave Forge server-side scripts maintained, for example list_packages.php and packages.php?
|
Tue 16 Jul 2013 06:19:01 PM UTC, comment #2:
In addition, the listing of packages doesn't bother to respect the pager - it just scrolls on and on ....
|
Sat 13 Jul 2013 09:18:59 PM UTC, comment #1:
Using a tic (); pkg -forge list; toc (), says
Which is faster than Rik's result, but still too slow (imo).
|
Sat 13 Jul 2013 05:40:33 PM UTC, original submission:
This is overwhelmingly slow and discourages using the built-in interface. It is faster to actually go to the octave-forge website to browse around.
The problem seems to be that get_forge_pkg is called on each package name and each call takes ~0.5 seconds. It might be easiest just to maintain a list of the Octave-Forge packages and their version numbers somewhere "magic" on the Octave-Forge site that the pkg command could fetch with urlread.
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one
Digest:
bug dependencies.
Follow 2 latest changes.