[pacman-dev] [PATCH] Add new SharedPkgCache option.

Roman Kyrylych roman.kyrylych at gmail.com
Sun Feb 17 11:14:56 EST 2008


2008/2/17, Xavier <shiningxc at gmail.com>:
> On Sun, Feb 17, 2008 at 05:37:13PM +0200, Roman Kyrylych wrote:
> > 2008/2/16, Chantry Xavier <shiningxc at gmail.com>:
> > > As it was already mentioned several times, the new -Sc behavior in 3.1 is
> > > great, but only when the package cache is not shared.
> > >
> > > When this option is enabled, -Sc will clean packages that are no longer
> > > available in any sync db, rather than packages that are no longer in the
> > > local db. The resulting behavior should be better for shared cache.
> > >
> >
> > Great name! :-)
> >
> > BTW, I've just realized that there might be a problem with "no longer
> > in any sync db" that, I think was not in 3.0's -Sc:
> > if SystemA has core,extra,community enabled and SystemB only
> > core&extra then doing -Sc on SystemB will cleanup community packages
> > from the shared cache.
> > I don't know if it's worth to fix this by using a more complicated
> > (filename comparison, AFAIR) aproach like in 3.0. :-/
> >
>
> Indeed, that's a problem, but don't know if it's a big one. I would think
> it's rather common to use the same set of sync db on a set of machines
> sharing pkg cache. And that approach is indeed much simpler.
>
> I mentioned this in the man page, that this option is rather meant for setup
> where same sync dbs are used.

Ah, OK, didn't read that. :-)
Then we can forget about this corner case,
it can be worked around by cache cleanup scripts based on filename parsing
(available on BBS and ML).

-- 
Roman Kyrylych (Роман Кирилич)


More information about the pacman-dev mailing list