From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: [DONE] Re: [gentoo-user] Portage metadata cache backend: sqlite or not?
Date: Fri, 12 Jun 2015 18:06:07 +0200 [thread overview]
Message-ID: <20150612180607.5bbf9650@thetick> (raw)
In-Reply-To: <20150504213353.411c112c@marcec.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Am Mon, 4 May 2015 21:33:53 +0200
schrieb Marc Joliet <marcec@gmx.de>:
> Oh wow, I completely forgot about this open thread. In my defense, I had to
> move out two (or was it three?) days after I started the thread, and didn't have
> internet again until over a month later.
>
> Am Wed, 13 Aug 2014 07:30:01 +0530
> schrieb Nilesh Govindrajan <me@nileshgr.com>:
>
> [...]
> > Having tried this feature, I'd advise against it. It takes long time
> > to generate metadata after sync and not really that advantageous. Also
> > eix has it's own issues in this mode.
>
> Do I understand correctly: you recommend switching away from the sqlite
> backend? Also, can you please elaborate on the issues with eix? I haven't
> noticed anything so far, but some bugs are easy to miss.
Well, there's no need to leave this thread dangling, so I went ahead and moved
away from sqlite, and have not noticed any regressions (or improvements, other
than faster syncing, because sqlite needs the metadata-transfer feature).
So I consider this thread done.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-06-12 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 18:10 [gentoo-user] Portage metadata cache backend: sqlite or not? Marc Joliet
2014-08-12 20:48 ` [gentoo-user] " James
2014-08-13 2:00 ` [gentoo-user] " Nilesh Govindrajan
2015-05-04 19:33 ` Marc Joliet
2015-06-12 16:06 ` Marc Joliet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150612180607.5bbf9650@thetick \
--to=marcec@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox