On Sat, 28 Dec 2019 21:19:18 -0500
Aaron Bauman wrote:
> Ah, you found the Achilles heel. It is much easier to postulate on the mailing
> list, use big words, and then say you just won't do that thing because
> tools/languages such.
>
> Perl though...
FTR: Even though I'm good at Perl, I
On Sat, Dec 28, 2019 at 10:05:02AM -0800, Alec Warner wrote:
> On Sat, Dec 28, 2019 at 3:43 AM Kent Fredric wrote:
>
> > On Sat, 28 Dec 2019 11:35:49 +
> > Michael 'veremitz' Everitt wrote:
> >
> > > Note: we're nnot acttually talking about replacing portage here, just
> > > creating a
On Sat, Dec 28, 2019 at 3:43 AM Kent Fredric wrote:
> On Sat, 28 Dec 2019 11:35:49 +
> Michael 'veremitz' Everitt wrote:
>
> > Note: we're nnot acttually talking about replacing portage here, just
> > creating a tool thiink php script web tthingy)) that will do some of
> > the
On Sat, 28 Dec 2019 11:40:08 +
James Le Cuirot wrote:
> Unfortunately a3li used Elasticsearch, which no one understands, but
> it's a start.
And I've used ES enough to say I would rather never use it again.
pgp7mS3HF7Z2A.pgp
Description: OpenPGP digital signature
On Sat, 28 Dec 2019 11:35:49 +
Michael 'veremitz' Everitt wrote:
> Note: we're nnot acttually talking about replacing portage here, just
> creating a tool thiink php script web tthingy)) that will do some of
> the pre-screeninng wok that AT hate (eg what kensiington did with
>
On Sun, 29 Dec 2019 00:27:36 +1300
Kent Fredric wrote:
> On Sat, 28 Dec 2019 11:14:15 +
> Michael 'veremitz' Everitt 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
> >
On 28/12/19 11:32, Kent Fredric wrote:
> On Sat, 28 Dec 2019 11:14:15 +
> Michael 'veremitz' Everitt 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
On Sat, 28 Dec 2019 11:14:15 +
Michael 'veremitz' Everitt 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
>
On Sat, 28 Dec 2019 11:14:15 +
Michael 'veremitz' Everitt 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
>
On 28/12/19 11:05, Kent Fredric wrote:
> On Sat, 28 Dec 2019 10:35:09 +0100
> Fabian Groffen wrote:
>
>> Hmmm, interested to hear what kind of things you're thinking about here.
> A lot of the "Work" of filing a keyword request is modelling all the
> consequential keywordings that have to take
On Sat, 28 Dec 2019 10:35:09 +0100
Fabian Groffen wrote:
> Hmmm, interested to hear what kind of things you're thinking about here.
A lot of the "Work" of filing a keyword request is modelling all the
consequential keywordings that have to take place.
If there was say, a web based UI, that:
-
On 28-12-2019 22:27:02 +1300, Kent Fredric wrote:
> On Sat, 28 Dec 2019 08:09:33 +0100
> Michał Górny wrote:
>
> > How can we improve this?
>
> Every time this kind of issue comes up, I can't help feeling we need
> some sort of tool more advanced than what we currently have.
>
> Something that
On Sat, 28 Dec 2019 08:09:33 +0100
Michał Górny wrote:
> How can we improve this?
Every time this kind of issue comes up, I can't help feeling we need
some sort of tool more advanced than what we currently have.
Something that maintains persistence of keyword demands similar to how
the current
13 matches
Mail list logo
