627012 – app-portage/flaggie-0.2.1 --sort mishandles semicolon USE flag syntax

Bug 627012 - app-portage/flaggie-0.2.1 --sort mishandles semicolon USE flag syntax

Summary: app-portage/flaggie-0.2.1 --sort mishandles semicolon USE flag syntax

Status:	RESOLVED UPSTREAM

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal
Assignee:	Michał Górny

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2017-08-04 00:15 UTC by Georgy Yakovlev
Modified:	2017-08-04 21:15 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Georgy Yakovlev archtester

2017-08-04 00:15:52 UTC

Here is quick case

> /etc/portage/package.use # flaggie --version
> flaggie 0.2.1`

and contets of a file
> /etc/portage/package.use # cat llvm
> sys-devel/clang LLVM_TARGETS: -NVPTX -AMDGPU
> sys-devel/llvm  LLVM_TARGETS: -NVPTX -AMDGPU

I run sort

> /etc/portage/package.use # flaggie --sort

and -AMDGPU gets moved in front of LLVM_TARGETS:

> /etc/portage/package.use # cat llvm
> sys-devel/clang -AMDGPU LLVM_TARGETS: -NVPTX
> sys-devel/llvm -AMDGPU LLVM_TARGETS: -NVPTX


I have not looked at the code myself yet, maybe that's something I can fix myself and submit a patch. Maybe not.

Comment 1 Georgy Yakovlev archtester

2017-08-04 03:55:39 UTC

I went to see the code and realized that there is an issue opened for that already
https://github.com/mgorny/flaggie/issues/13
what should I do with this bug?

Comment 2 Michał Górny archtester

2017-08-04 21:15:52 UTC

I track flaggie issues at GitHub. Long story short, the USE flag rework is WIP but I have so much on my plate that I don't even remember how far it's gotten. I'm sorry but please don't expect a complete fix anytime soon.

I think the current git (-9999) has a partial support for USE_EXPAND groups in package.use. However, I think I've disabled all the cleanup actions there as they don't support it yet.