Talk:TIP speed up portage with sqlite

From Gentoo Linux Wiki

Jump to: navigation, search

Is it faster then cdb?

I suppose, it's a bit slower than cdb, but still much faster than the default flat files. And sqlite is supported by portage directly without any hacks, so I prefer to switch to sqlite now.

Are there any plans to make this the default for portage at any point? It makes a lot more sense than flat files (and just sped up my dependency checking a huge amount). 66.167.88.25 21:12, 23 May 2007 (UTC)



This breaks best_version and has_version causing an access violation to /var/cache/edb/dep/usr/portage.sqlite (for example, merging ftpbase or svgalib).

hi, h0m3r

Contents

[edit] @homer

can you describe the errors more precisely please?

i can merge ftpbase and svgalib without problems

[edit] gtaluvit

I use sqllite for portage and I've seen the same issue. For ebuilds that fail, I use FEATURES=-sandbox emerge -av <package>.

[edit] sandbox violations

seems to be only a problem on amd64 arch... i'am using sqlite on x86 and amd64, but only on amd64 best_version and has_version fails

i've used the same FEATURES to test the behaviour

FEATURES="autoconfig ccache cvs distlocks metadata-transfer parallel-fetch sandbox sfperms strict userfetch userpriv usersandbox"

maybe it's a portage bug which affects not only sqlite but any fsbased caching method?

[edit] Both versions

Actually, I have both a x86 and an amd64 box and they both will have the same issue with the sandbox. I don't know why.

Features for AMD64:

FEATURES="autoconfig distlocks metadata-transfer noinfo parallel-fetch sandbox sfperms strict"

Features for x86:

FEATURES="autoconfig distlocks metadata-transfer noinfo parallel-fetch sandbox sfperms strict"

[edit] "The only known solution is to comment out the db modules in /etc/portage/modules and redo updating!"?

In the Problems section, I find: "The only known solution is to comment out the db modules in /etc/portage/modules and redo updating!". To what problem is this the solution? Installing works perfectly fine without FEATURES=-collision-protect, so I doubt that this is the problem to which this was the solution. --A.skwar 11:22, 2 October 2006 (UTC)

[edit] @This Breaks Kuroo - jacob_AT_jacobeiler.net

For users of software like Kuroo for package management, this breaks Kuroo. Do you know of a solution? I have reported this as a bug in Kuroo. I can be contacted at the above email address in the title.

Oh, also, has the modules location changed or something? I didn't have the modules file and had to create it, and just wondered if it were supposed to go somewhere else, like in a config file. Can you help me?

Personal tools