FS#7339 - Allow more than one cache dir

Attached to Project: Pacman
Opened by dtw (dibblethewrecker) - Saturday, 02 June 2007, 09:41 GMT
Last edited by Dan McGee (toofishes) - Friday, 05 October 2007, 01:16 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.0.4
Due in Version 3.1.0
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

To reduce bandwidth it would be great if it was easier to share downloaded pkgs with other machines. My solution, using unionfs, to combine two cache dirs was ok but unionfs is too unstable.

A pacman option to check an extra cache dir for previously downloaded pkgs would make things a whole lot easier. The standard cache dir remains RW, i.e. new pkgs go there, but being able to grab files from an existing cache on top of that would be great.

This is a fairly easy one I would guess.
This task depends upon

This task blocks these from closing
 FS#8109 - Pacman 3.1 Release Roadmap 
Closed by  Dan McGee (toofishes)
Friday, 05 October 2007, 01:16 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in 3.1, currently in GIT
Comment by Dan McGee (toofishes) - Saturday, 02 June 2007, 14:51 GMT
Any reason these kind of things shouldn't be a pacman.conf setting anyway? It would be nice to not have to hardcode more than one path in the pacman binary.

Specifying two cache dirs would then be allowed, it would be a fallback thing in the same way the server lists currently are. Check the first for the file, then check the second. Download, try to store it in the first, then try to store it in the second, etc.

Other prefs for pacman.conf:
* lockfile location
* db location
Comment by dtw (dibblethewrecker) - Thursday, 07 June 2007, 17:34 GMT
That sounds great to me, Dan. Phrak contacted me a while back about my bandwidth saving scripts but being able to NFS a generic cache would be a real bonus. Also, I always wondered why some many paths were hard-coded.
Comment by Dan McGee (toofishes) - Saturday, 09 June 2007, 17:31 GMT
Pushed to the archlinux.org git tree. Requires a bit of testing.

Loading...