[solved] Any problems sharing pkg cache between 64/32-bit systems?

ngoonee · 2010-07-12 05:06:29

With the advent of the -any- package, there'd be some minor space savings if I had my 32-bit chroot cache in /var/cache/pacman/pkg together with my 64-bit system. Anyone has any warnings about possible problems with this approach?

I see it as quite simple, no 32-bit/64-bit packages would overwrite the other architecture packages, neither would 32/64-bit pacman try to install the wrong architecture (due to uname -m being used on the 'auto' architecture). -any- packages would be shared between the both of them, meaning only one download needed between both, and only a single storage space.

My concern is that I wouldn't be able to pacman -Sc anymore? Any possible workarounds for that? The other thing I thought about doing was having a pacman hook (not implemented yet I know, but I'd 'implement' it using a script) was hard-linking -any- packages after every pacman update. More complex and easier to break, but would allow pacman -Sc no problem.

Allan · 2010-07-12 05:12:58

pacman -Sc is the only issue. I once had a cron daemon putting hardlinks in the other pkgcache every so often, but now I only do it when I rsync some repos to my pkcache...

ngoonee · 2010-07-12 09:25:25

Thanks Allan. I recall Xyne having some sort of 'keep last X packages' python app, maybe I'll bug him to add a simple 'ignore packages not of the right architecture' and use that.

tomk · 2010-07-12 11:34:43

I've done this for years, before -any packages existed - I just manage my cache outside of pacman.

ngoonee · 2010-07-12 11:45:55

tomk wrote:

I've done this for years, before -any packages existed - I just manage my cache outside of pacman.

Manually? Or with personal scripts? If the latter would you mind sharing them?

tomk · 2010-07-12 13:35:20

yeah, guess I should have mentioned that..

I do it manually - about twice a year, and each time I say "I really should script that"...

Snowman · 2010-07-12 21:21:45

tomk wrote:

yeah, guess I should have mentioned that..
I do it manually - about twice a year, and each time I say "I really should script that"...

I also do it manually whenever I need HD space.

Another issue is old packages in the repo that don't have the arch in their package name. Pacman complains about mismatched md5sums so you need to tell it to removed the package and redownload it. It's just an annoyance that will soon disappear as we are currently rebuilding the old community packages.

ngoonee · 2010-07-12 23:08:00

tomk wrote:

yeah, guess I should have mentioned that..
I do it manually - about twice a year, and each time I say "I really should script that"...

Can I say 'ouch'.......

Arch Linux

#1 2010-07-12 05:06:29

[solved] Any problems sharing pkg cache between 64/32-bit systems?

#2 2010-07-12 05:12:58

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

#3 2010-07-12 09:25:25

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

#4 2010-07-12 11:34:43

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

#5 2010-07-12 11:45:55

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

#6 2010-07-12 13:35:20

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

#7 2010-07-12 21:21:45

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

#8 2010-07-12 23:08:00

Re: [solved] Any problems sharing pkg cache between 64/32-bit systems?

Board footer