Ticket #406 (new support-request)

Opened 10 years ago

read-only name caches

Reported by: impulze Owned by: ciaranm
Priority: Sometime Milestone:
Component: clients/paludis Version: 0.24.6
Keywords: Cc:
Blocked By: Blocking:
Distribution:

Description

I wonder if it would be possible to have either a seperate cache handling or another nifty thing to disable regenerating the cache on your local system. In my situation i have a NFS share which shares the repositories (which get synced on a remote box). Thus the names_cache (which is configured to be in the repository) is shared too and it would be a no brainer to re-generate your cache locally because it's already done after the sync on the remote box. Secondly the share is read-only and the cache therefore can't be regenerated. I still would like to be able to regenerate the cache of my local repositories which are stored on another location. So either a seperate cache regeneration or some nifty read-only option in a repositories configuration file would be great. There may be much better solutions to this but i couldn't think of any so far. Is there any interest in supporting this?

Note: See TracTickets for help on using tickets.