[gentoo-dev] ekeyword written in python from scratch

[gentoo-dev] ekeyword written in python from scratch

[Mike Frysinger]

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

i finally got annoyed with the perl version (and its output and bugs and 
limitations) and wrote a new version.  it's fairly modular (and has pretty 
good unittest coverage!?), so if we wanted to look at integrating it into 
portage or other tools, that should be pretty easy now.

at any rate, if other devs who use this want to give it a crack, that'd be 
great.  iron out bugs before the next release.
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=blob_plain;f=src/ekeyword/ekeyword.py;hb=gentoolkit-
dev
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] ekeyword written in python from scratch

[Ulrich Mueller]

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

>>>>> On Mon, 20 Jan 2014, Mike Frysinger wrote:

> i finally got annoyed with the perl version (and its output and bugs
> and limitations) and wrote a new version. it's fairly modular (and
> has pretty good unittest coverage!?), so if we wanted to look at
> integrating it into portage or other tools, that should be pretty
> easy now.

> at any rate, if other devs who use this want to give it a crack,
> that'd be great. iron out bugs before the next release.
> http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=blob_plain;f=src/ekeyword/ekeyword.py;hb=gentoolkit-dev

Sorting order is different from the present ekeyword. The part after
the hyphen (or the empty string if there is no hyphen) should be used
as primary key and the part before the hyphen as secondary key.
That is, keyword ordering should be:

   amd64 x86 amd64-fbsd x86-fbsd amd64-linux x86-linux ppc-macos

You currently have:

   amd64 x86 amd64-fbsd amd64-linux ppc-macos x86-fbsd x86-linux

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-dev] ekeyword written in python from scratch

[Mike Frysinger]

[-- Attachment #1: Type: Text/Plain, Size: 387 bytes --]

On Monday 20 January 2014 04:16:23 Ulrich Mueller wrote:
> Sorting order is different from the present ekeyword. The part after
> the hyphen (or the empty string if there is no hyphen) should be used
> as primary key and the part before the hyphen as secondary key.

hmm, was unaware of that.  should be fixed now.  added your example as a 
unittest to prevent regression.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] ekeyword written in python from scratch

[Jeroen Roovers]

On Mon, 20 Jan 2014 01:01:40 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> at any rate, if other devs who use this want to give it a crack,
> that'd be great.  iron out bugs before the next release.
> http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=blob_plain;f=src/ekeyword/ekeyword.py;hb=gentoolkit-
> dev

# cp nvidia-drivers-304.117.ebuild nvidia-drivers-304.119.ebuild
# ~/bin/ekeyword ~all nvidia-drivers-304.119.ebuild
nvidia-drivers-304.119: -~* ~amd64 ~x86 ~amd64-fbsd ~x86-fbsd

It's more obvious with the fancy colouring, but here it removes -* and
adds ~*.


Regards,
     jer

Re: [gentoo-dev] ekeyword written in python from scratch

[Mike Frysinger]

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

On Monday, January 27, 2014 14:01:58 Jeroen Roovers wrote:
> # cp nvidia-drivers-304.117.ebuild nvidia-drivers-304.119.ebuild
> # ~/bin/ekeyword ~all nvidia-drivers-304.119.ebuild
> nvidia-drivers-304.119: -~* ~amd64 ~x86 ~amd64-fbsd ~x86-fbsd
> 
> It's more obvious with the fancy colouring

if you dislike the color format, then pick a different one.  there are a large 
number available.

> but here it removes -* and adds ~*.

this should fix it:
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commitdiff;h=465c0532f88df7bf3af08e84172ea5a908105fc1
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-dev] ekeyword written in python from scratch

[Jeroen Roovers]

On Mon, 27 Jan 2014 18:14:54 -0500
Mike Frysinger <vapier@gentoo.org> wrote:

> > It's more obvious with the fancy colouring
> 
> if you dislike the color format, then pick a different one.  there
> are a large number available.

I didn't intend that at all. A coloured multiline output would be a nice
default, though, since not everyone/everywhere is able to display/read
in colours.


     jer

Re: [gentoo-dev] ekeyword written in python from scratch

[Mike Frysinger]

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

On Tuesday, January 28, 2014 05:53:52 Jeroen Roovers wrote:
> On Mon, 27 Jan 2014 18:14:54 -0500 Mike Frysinger wrote:
> > > It's more obvious with the fancy colouring
> > 
> > if you dislike the color format, then pick a different one.  there
> > are a large number available.
> 
> I didn't intend that at all. A coloured multiline output would be a nice
> default, though, since not everyone/everywhere is able to display/read
> in colours.

the script respects portage's NOCOLOR setting as well as its color map.  so if 
you've configured your system correctly, it should automatically pick a usable 
format (and use colors you're used to).

if you can't handle colors and you don't have NOCOLOR turned on, then not much 
i can do about that ;).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]