Summary: | 'xml' and 'expat' USE flags confusing | ||
---|---|---|---|
Product: | Quality Assurance | Reporter: | Joe Breuer <gentoo> |
Component: | Disputes/raising issues | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | UNCONFIRMED --- | ||
Severity: | QA | CC: | hasufell, mmokrejs, pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
List of packages using the 'xml' USE flag
List of packages using the 'expat' USE flag |
Description
Joe Breuer
2013-07-15 15:09:42 UTC
can you give some more specific examples? Created attachment 353356 [details]
List of packages using the 'xml' USE flag
Created attachment 353358 [details]
List of packages using the 'expat' USE flag
At least sys-devel/gdb, app-arch/rpm5, x11-wm/matchbox-window-manager, media-video/kmplayer seem to use 'expat' to enable XML support. In net-libs/neon, 'expat' toggles between expat and libxml2. net-misc/sitecopy evaluates both 'xml' and 'expat' and apparently toggles, but to be frank I don't really understand what the intended result is. Most of the other packages in my list I don't know well enough to be able to say what they do with expat. I guess packages should tend to use "xml" when possible and only "expat" to allow choosing between the implementations, right? |