| 1 |
On Mon, Sep 28, 2009 at 08:23:34PM +0200, Sebastian Pipping wrote: |
| 2 |
> Hello there! |
| 3 |
> |
| 4 |
> |
| 5 |
> This may look like like a lot of text but it actually isn't. |
| 6 |
> Please read on. Thanks. |
| 7 |
|
| 8 |
Thanks for your good work. |
| 9 |
I agree with your changes it was indeed needed. |
| 10 |
|
| 11 |
Actually, during my GSOC, I've noted layman-global.txt should be changed |
| 12 |
to have a cleanier description information and it's probably the moment |
| 13 |
to introduce this. |
| 14 |
|
| 15 |
At the moment, <description> is used for very short descriptions: |
| 16 |
<description>Arcon Overlay!</description> |
| 17 |
or quite longer: |
| 18 |
<description>A collection of Bazaar-related ebuilds, including release candidates of Bazaar.</description> |
| 19 |
even ery long: |
| 20 |
<description>Berkano overlay provides an overlay for Gentoo Linux with |
| 21 |
ebuilds of bleeding edge software (such as live subversion builds) and other handy tools that are missing from the official portage tree. Areas of interest include multimedia and system administration.</description> |
| 22 |
|
| 23 |
layman is a cli so it doesn't really care of the description lenght but |
| 24 |
it's a pain to use in a GUI like PackageKit repository list. I think we |
| 25 |
should introduce a <longdescription> field even with a lang parameter |
| 26 |
like we already have in metadata.xml. So, description field will have to |
| 27 |
be used for short descriptions (a few words) to complete the name of the |
| 28 |
overlay like: |
| 29 |
<description>experimental gnome ebuilds</description> |
| 30 |
|
| 31 |
I don't think DTD have abilities to restrict field value lenght but even |
| 32 |
if we will have to change a few <description> by hands, having a |
| 33 |
<longdescription> field could help. |
| 34 |
|
| 35 |
Sebastian, do you think you can add this to your set of changes ? (only |
| 36 |
the new field in the DTD at the moment). |
| 37 |
|
| 38 |
Thanks, |
| 39 |
Mounir |
Archives