public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keywordreqs and slacking arch teams
Date: Sat, 28 Dec 2019 11:40:08 +0000	[thread overview]
Message-ID: <20191228114008.1edf0331@symphony.aura-online.co.uk> (raw)
In-Reply-To: <20191229002736.0d53aaa6@katipo2.lan>

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

On Sun, 29 Dec 2019 00:27:36 +1300
Kent Fredric <kentnl@gentoo.org> wrote:

> On Sat, 28 Dec 2019 11:14:15 +0000
> Michael 'veremitz' Everitt <gentoo@veremit.xyz> wrote:
> 
> > I know I'm gonna be shot down in flames, because $heresy, but here is where
> > a package 'database' would actually work quite well, because you can
> > trivially create a query that pulls this data out, and sorts it by package
> > category or maintainer or whatever you like ..
> > 
> > Ok, let the flamewars begin ...  
> 
> There's no real problem with a package database, however, the real
> limitation is in the ebuild source format, which ultimately means any
> such database needs a lot of bash-sourcing hell to simply stay
> up-to-date ( any time an eclass changes, the interpretation of every
> ebuild that uses it also changes, necessitating some pretty fun(1) code )
> 
> And that winds you up fighting with portage internals.
> 
> So simply, in order for somebody like me to actually implement such a
> thing, a precursory step is to rewrite enough portage to do just that.
> 
> But I haven't (yet) gotten around to that.
> 
> 
> 1: Not actually fun.

Doesn't https://packages.gentoo.org already have such a database?
Unfortunately a3li used Elasticsearch, which no one understands, but
it's a start.

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-12-28 11:40 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28  7:09 [gentoo-dev] Keywordreqs and slacking arch teams Michał Górny
2019-12-28  9:27 ` Kent Fredric
2019-12-28  9:35   ` Fabian Groffen
2019-12-28 11:05     ` Kent Fredric
2019-12-28 11:14       ` Michael 'veremitz' Everitt
2019-12-28 11:27         ` Kent Fredric
2019-12-28 11:40           ` James Le Cuirot [this message]
2019-12-28 11:44             ` Kent Fredric
2019-12-28 11:32         ` Kent Fredric
2019-12-28 11:35           ` Michael 'veremitz' Everitt
2019-12-28 11:42             ` Kent Fredric
2019-12-28 18:05               ` Alec Warner
2019-12-29  2:19                 ` Aaron Bauman
2019-12-29  5:09                   ` Kent Fredric
2019-12-30  1:45         ` A Schenck
2020-01-02 20:32       ` Rolf Eike Beer
2020-01-02 23:25         ` Mike Pagano
2020-01-02 23:35           ` Rolf Eike Beer
2020-01-03  0:19             ` Michael 'veremitz' Everitt
2020-01-03  2:40             ` Aaron Bauman
2020-01-03 10:00               ` Rolf Eike Beer
2020-01-04 11:09                 ` Rolf Eike Beer
2020-01-04 11:25                   ` Michael 'veremitz' Everitt
2020-01-04 13:35                     ` Rolf Eike Beer
2020-01-03 14:37             ` [gentoo-dev] Vanilla sources Michael Orlitzky
2020-01-03 14:40               ` Toralf Förster
2020-01-03 14:41                 ` Michael Orlitzky
2020-01-03 14:46                   ` Rich Freeman
2020-01-03 14:48                     ` Toralf Förster
2020-01-03 22:32                       ` Michael 'veremitz' Everitt
2020-01-04  7:38                       ` Hanno Böck
2020-01-04 18:39                         ` William Hubbs
2020-01-04 18:41                         ` Michał Górny
2020-01-07  8:52                           ` Hanno Böck
2020-01-03 14:52                     ` Michael Orlitzky
2020-01-03 14:55                       ` Michael Orlitzky
2020-01-03 16:28                         ` Aaron Bauman
2020-01-04 11:01                           ` Rich Freeman
2020-01-04 11:42                             ` Roy Bamford
2020-01-04 12:54                               ` Rich Freeman
2020-01-04 13:08                                 ` Roy Bamford
2020-01-04 13:43                                   ` Thomas Deutschmann
2020-01-05 10:34                                     ` Roy Bamford
2020-01-04 20:13                                 ` Christopher Head
2020-01-04 20:39                                   ` Rich Freeman
2020-01-04 13:47                             ` Thomas Deutschmann
2020-01-04 18:41                         ` William Hubbs
2020-01-04 18:42                           ` Michał Górny
2020-01-04 19:13                           ` Rolf Eike Beer
2020-01-05 16:41                             ` Michael Orlitzky

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=20191228114008.1edf0331@symphony.aura-online.co.uk \
    --to=chewi@gentoo.org \
    --cc=gentoo-dev@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