bugGNU Octave - Bugs: bug #55873, pkg: cache download package files

 
 

bug #55873: pkg: cache download package files

Submitter:  Andrew Janke <apjanke>
Submitted:  Sat 09 Mar 2019 06:49:21 PM UTC
 
Category:  Octave Function Severity:  1 - Wish
Priority:  3 - Low Item Group:  Feature Request
Status:  None Assigned to:  None
Originator Name:  Open/Closed:  * Open
Release:  * dev Operating System:  * Any
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Sat 09 Mar 2019 08:42:19 PM UTC, comment #5: 

@philip I think everything you asked is covered by

> On GNU/Linux, macOS, and Unix systems: ${XDG_CACHE_HOME:-~/.cache}/octave/...

Mike Miller <mtmiller>
Project Administrator
Sat 09 Mar 2019 08:40:51 PM UTC, comment #4: 

Could the actual location be made adjustable, with the system-dependent defaults suggested as e.g., in comment #2 ? Maybe through an environment setting or a system-wide pref in share/octave/site/m/startup/

BTW, I'd second %LOCALAPPATA% on Windows systems (as %APPDATA% isn't meant for large(r) files cf. the specs in:
https://docs.microsoft.com/en-us/windows/uwp/design/app-settings/store-and-retrieve-app-data )
(although admittedly my own roaming profile at work is several 100s of MBs and on this home PC it is >700 MB.)

What would the optimal location on Mac OSX be?

Philip Nienhuis <philipnienhuis>
Project Member
Sat 09 Mar 2019 07:28:39 PM UTC, comment #3: 

> Would this only apply to '-forge' installs, or to any install that looks like a URL?


I'm less inclined to cache non-forge installs, because they may be changing rapidly. For example, https://github.com/apjanke/octave-table/archive/master.zip or any other Git master URL could be receiving new commits quite often.

> Should also be a way to bypass or clear the cache?


Definitely a clear command; maybe a bypass option. A bypass option would get rid of the above concern. But users would have to know to enable it.

Your paths look good to me.

Andrew Janke <apjanke>
Sat 09 Mar 2019 07:19:25 PM UTC, comment #2: 

Full agree. Would this only apply to '-forge' installs, or to any install that looks like a URL? Should also be a way to bypass or clear the cache?

On GNU/Linux, macOS, and Unix systems: ${XDG_CACHE_HOME:-~/.cache}/octave/...

On Windows: %LOCALAPPDATA%\octave\cache\...

This is based on the QStandardPaths::CacheLocation cross-platform logic.

Mike Miller <mtmiller>
Project Administrator
Sat 09 Mar 2019 06:51:20 PM UTC, comment #1: 

This is following up discussion in bug #36477.

Andrew Janke <apjanke>
Sat 09 Mar 2019 06:49:21 PM UTC, original submission:  

It would be nice if pkg would cache its downloaded files somewhere.

This would speed up downloads for users on slow internet connections.

And as a minor GUI improvement, it would get rid of the temporary files flying in and out of the "Current Directory" display when you do a `pkg -forge` installation.

Somewhere under $XDG_CACHE_HOME, like `$XDG_CACHE_HOME/octave/pkg/downloads` would be an appropriate place on Unix. Somewhere under %LOCALAPPDATA% on Windows.

Low priority.

Andrew Janke <apjanke>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by apjanke (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only project members can vote.

     

     

     

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-03-09 mtmiller CategoryLibraries Octave Function
        Severity3 - Normal 1 - Wish
        Priority5 - Normal 3 - Low
        Releaseother dev

    Back to the top


    Powered by Savane 3.9