| 1 |
Jan Kundrát <jkt@g.o> writes: |
| 2 |
|
| 3 |
> But also the need to replicate http://www.kde.org/ to metadata.xml of |
| 4 |
> all KDE split ebuilds -- right now, this is set by an eclass. |
| 5 |
|
| 6 |
The usefulness of this is IMHO debatable; why not just writing it one |
| 7 |
package (say kde-base/kde or kde-meta) and just there? Having each |
| 8 |
mini-package express itself as having that as its homepage is not very |
| 9 |
useful to me, but I guess it's debatable. |
| 10 |
|
| 11 |
>> - allows proper handling of packages lacking a HOMEPAGE; |
| 12 |
> |
| 13 |
> Could you elaborate a bit about how different is handling of an |
| 14 |
> empty/uninitialized shell variable from an empty XML element? |
| 15 |
|
| 16 |
That you can provide _other_ links beside an homepage, like |
| 17 |
"unmaintained", "gentoo:userguide" and stuff like that so that user |
| 18 |
don't just get no homepage at all, and they are not misdirected by |
| 19 |
homepage being http://www.gentoo.org/ or something. |
| 20 |
|
| 21 |
>> - users can check the metadata much more easily by just opening the xml |
| 22 |
>> file or interfacing to that rather than having to skim through the |
| 23 |
>> ebuild, the xml files are probably more user readable then ebuilds |
| 24 |
>> using multiple eclasses; |
| 25 |
> |
| 26 |
> Haven't we already agreed that accessing ebuilds/... directly is |
| 27 |
> broken by design? |
| 28 |
|
| 29 |
For a software sure, but as an user I am automatically brought to just |
| 30 |
look at the files if I'm looking for the homepage of a package I know, |
| 31 |
and seeing a metadata.xml file I'm more likely to look at that rather |
| 32 |
than the metadata cache in /var/db/... . |
| 33 |
|
| 34 |
And it's certainly more user-readable an XML file than HOMEPAGE with |
| 35 |
depend-like syntax for labels and conditionals and whatever else seems |
| 36 |
like Alec is proposing for EAPI=3 |
| 37 |
|
| 38 |
>> - webapps like packages.gentoo.org would be able to display basic |
| 39 |
>> information without having to parse the ebuilds or the metadata cache. |
| 40 |
> |
| 41 |
> Except for the ebuilds which still use the old format (that is 100% of |
| 42 |
> the tree right now) |
| 43 |
|
| 44 |
This of course is meant as "whenever this is fully implemented" |
| 45 |
|
| 46 |
-- |
| 47 |
Diego "Flameeyes" Pettenò |
| 48 |
http://blog.flameeyes.eu/ |
Archives