From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Application name in metadata.xml
Date: Tue, 14 Feb 2012 06:24:11 +1300 [thread overview]
Message-ID: <CAATnKFAmXArh=gLYK61P-SUptuJAfuW963GJLRT15g3EfrUnPg@mail.gmail.com> (raw)
In-Reply-To: <4F38CB49.2060302@gentoo.org>
On 13 February 2012 21:35, Markos Chandras <hwoarang@gentoo.org> wrote:
> This field wont be useful to users but to GUI applications that want
> to show a pretty name instead of a weird PN. It would be fully
> optional but it would have a standard syntax. You can't use
> <longdesription> for that to extract the real package name because
> each developer use this tag in a different way. Same for description.
> The proposed tag would have a single strict syntax, that is a single
> string just for the real package name so it would be easily
> extractable. And of course it would be fully optional. After all, it
> is just an addition in metadata.dtd
>
I think it makes sense to also support there being multiple fields of
this kind, because packages like libreoffice bundle multiple
applications in the one.
I'd propose a structure like
<provides>
<application name="Libreoffice Writer" binary="lowriter"
description="A Word processing tool">
</application>
....
</provides>
You could have a proviso somewhere for multiple provides sections and
each section being dependent on some atom match, but I think that's
really over-engineering it.
I thought about putting in stuff to allow for extra metadata for
aliases and such to relate to what people are really looking for ( ie:
people who are still wanting openoffice should get given libreoffice
as a result ) but also smells of over-engineering and nasty messes.
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
next prev parent reply other threads:[~2012-02-13 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 13:00 [gentoo-dev] RFC: Application name in metadata.xml Fabio Erculiani
2012-02-11 13:27 ` Michał Górny
2012-02-11 14:03 ` Fabio Erculiani
2012-02-12 0:02 ` Ian Stakenvicius
2012-02-12 8:01 ` Fabian Groffen
2012-02-12 15:43 ` "Paweł Hajdan, Jr."
2012-02-12 19:37 ` Ulrich Mueller
2012-02-12 21:14 ` Alexandre Rostovtsev
2012-02-12 21:22 ` Michał Górny
2012-02-12 21:34 ` Alexandre Rostovtsev
2012-02-12 21:43 ` James Broadhead
2012-02-13 0:42 ` Thomas Sachau
2012-02-13 8:35 ` Markos Chandras
2012-02-13 13:12 ` Fabio Erculiani
2012-02-13 17:24 ` Kent Fredric [this message]
2012-02-13 9:41 ` Luca Barbato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAATnKFAmXArh=gLYK61P-SUptuJAfuW963GJLRT15g3EfrUnPg@mail.gmail.com' \
--to=kentfredric@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox