Summary: | app-admin/eselect: profile.eselect: support long descriptions of profiles | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | SpanKY <vapier> |
Component: | eselect | Assignee: | Gentoo eselect Team <eselect> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | pchrist, yngwin |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SpanKY
2012-10-30 08:16:43 UTC
This could be done if the information was available from some file that is easy to parse from bash. If it's XMl, then I don't think that adding things like XML-XPath to eselect's dependencies is a godd idea. (In reply to comment #1) inventing another file format when we already have a standard (and one that supports localization) doesn't seem like a good idea i don't see a problem with having an optional USE=xml in eselect and if the user builds it with USE=-xml, it uses sed to dump the first entry if xml --version >/dev/null; then echo `xml sel -t -m pkgmetadata -v longdescription ${metadata_xml}` else tr '\n' ' ' < ${metadata_xml} | \ sed -r 's:.*<longdescription[^>]*>([^<]*).*:\1:' fi |