summaryrefslogtreecommitdiff
blob: 57bfa198e59700d09ee0eef91e5b55a26ab500de (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
---
GLEP: 5
Title: Extending metadata.xml
Author: Heinrich Wendel <sysop@heinospage.de>
Type: Standards Track
Status: Deferred
Version: 1
Created: 2003-07-02
Last-Modified: 2014-01-17
Post-History: 2003-07-02, 2004-11-11
Content-Type: text/x-rst
---


Abstract
========

As the latest development in Gentoo and Portage added the metadata.xml file
to each package, which provides information about the package and its
maintainers, this GLEP proposes to extend this format in order to simplify
the .ebuild format.


Status
======

Timed out


Motivation
==========

The metadata.xml [1]_ standard was accepted and it already contains some
information about the packages (longdescription).


Specification
=============

Add the tags <description> <homepage> <license> to the metadata.xml [1]_ and
remove them from the .ebuild files.  All ebuilds and the emerge -S feature
have to be changed to use the new format.


Rationale
=========

The three tags description, homepage and license are mostly the same in all
versions of an ebuild, but they must be added to each version. In order to
simplify the .ebuild format they can be moved to the new metadata.xml [1]_ file.
This would also allow different descriptions for different languages (lang
attribute) and there are no problems when a program changes it license
(restrict attribute).


Backwards Compatibility
=======================

As it will take some time to do the changes on every ebuild, portage should still
support the old format for some time.


Reference Implementation
========================

not yet ...


References
==========

.. [1] Gentoo Herds Project
   [http://www.gentoo.org/proj/en/metastructure/herds/#doc_chap2]

Copyright
=========

This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
Unported License.  To view a copy of this license, visit
http://creativecommons.org/licenses/by-sa/3.0/.