From: "Michał Górny" <mgorny@gentoo.org>
To: Johannes Huber <johu@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metadata.xml GLEP for review
Date: Fri, 18 Mar 2016 20:57:43 +0100 [thread overview]
Message-ID: <20160318205743.22366e0a.mgorny@gentoo.org> (raw)
In-Reply-To: <11696691.uk7b88IGVO@rioja>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On Fri, 18 Mar 2016 20:42:59 +0100
Johannes Huber <johu@gentoo.org> wrote:
> Am Mittwoch 16 März 2016, 19:43:21 schrieb Michał Górny:
> > Hello, all.
> >
> > Long story short: while working on various metadata.xml-related
> > aspects, it bite us pretty hard that we lack proper spec for
> > metadata.xml file. What we have is pretty much the DTD, some partial
> > GLEPs (that sometimes provide incorrect info) and random bugs. ml
> > posts...
> >
> > Therefore, I've been slowly writing a proper GLEP that would describe
> > all of metadata.xml in detail. Here's the current draft for review:
> >
> > https://wiki.gentoo.org/wiki/User:MGorny/GLEP:68
>
> Hello Michal,
>
> just a crazy idea came to my mind: How about to add HOMEPAGE and DESCRIPTION
> from ebuild to metadata.xml. So that this duplicated info in ebuilds can be
> dropped in future EAPI?
It's outside the scope of what I'm doing and it's controversial. I'd
rather not delay clarifying the format for future ideas, especially
considering that there was no success so far in moving this one
forward.
--
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
prev parent reply other threads:[~2016-03-18 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 18:43 [gentoo-dev] metadata.xml GLEP for review Michał Górny
2016-03-16 19:37 ` Dirkjan Ochtman
2016-03-16 19:45 ` Michał Górny
2016-03-18 14:37 ` Michał Górny
2016-03-18 19:42 ` Johannes Huber
2016-03-18 19:57 ` Michał Górny [this message]
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=20160318205743.22366e0a.mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=johu@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