From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Annoying structure of /var/db/pkg/<category>/<package-name> database
Date: Fri, 10 May 2013 17:46:19 +0200 [thread overview]
Message-ID: <518D164B.3050107@googlemail.com> (raw)
In-Reply-To: <418374.63006.bm@smtp111.sbc.mail.gq1.yahoo.com>
Am 10.05.2013 04:59, schrieb Thomas Mueller:
> Having package data in /var/db/pkg/<category>/<package-name> carries the nuisance factor that finding a package involves a fishing expedition through many possible categories.
>
> I am spoiled by having /var/db/pkg/<package-name> in NetBSD pkgsrc and FreeBSD ports, though FreeBSD is wsitching to a different structure nkwon as pkgng.
>
> Is there any way to configure so as to avoid this annoyance in Gentoo? Like maybe making /var/db/pkg/<package-name>?
>
> One can do
> ls /var/db/pkg/*/<package-name> but this is still an annoyance.
>
> I have some limited experience with Gentoo Linux on my older computer. Compiling the kernel took 130 minutes, and then the kernel failed to boot.
>
> Tom
>
>
> .
>
and how do you deal with the problem of several packages having the same
name?
Or.. you don't look at that stuff, besides some cases of severe damage
control, you never have to go there?
next prev parent reply other threads:[~2013-05-10 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 2:59 [gentoo-user] Annoying structure of /var/db/pkg/<category>/<package-name> database Thomas Mueller
2013-05-10 3:07 ` staticsafe
2013-05-10 7:18 ` Marc Joliet
2013-05-10 8:15 ` Dale
2013-05-10 13:41 ` Marc Joliet
2013-05-10 16:35 ` Mark David Dumlao
2013-05-10 19:16 ` Dale
2013-05-10 8:54 ` Neil Bothwick
2013-05-10 15:46 ` Volker Armin Hemmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-08 11:05 Thomas Mueller
2013-05-08 11:37 ` Michael Hampicke
2013-05-08 11:41 ` Randolph Maaßen
2013-05-08 12:28 ` Neil Bothwick
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=518D164B.3050107@googlemail.com \
--to=volkerarmin@googlemail.com \
--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