| 1 |
On 11-02-2012 19:02:12 -0500, Ian Stakenvicius wrote: |
| 2 |
> On Sat, 11 Feb 2012 14:00:38 +0100 Fabio Erculiani |
| 3 |
> <lxnay@g.o> wrote: |
| 4 |
>> I think this is not the first time it's been discussed here, but |
| 5 |
>> maybe I'm wrong. Other distros associate a more user-friendly |
| 6 |
>> package name (application name) to packages. Say, they bind |
| 7 |
>> libreoffice-writer to "LibreOffice Writer" in package metadata. |
| 8 |
> |
| 9 |
> I don't think it's about being unambiguous, I think it's about |
| 10 |
> providing a common language title for the package. I could see this |
| 11 |
> as being something desirable for a portage gui or to add more |
| 12 |
> descriptive results to a search engine. |
| 13 |
> |
| 14 |
> That said, I expect there would need to be a near-portage-wide |
| 15 |
> adoption of the new entry for this to be useful in either case, and I |
| 16 |
> don't see that happening... |
| 17 |
|
| 18 |
I wonder if metadata.xml could be "regenerated" during rsync generation |
| 19 |
to include this entry if not present yet. It seems some simple rules |
| 20 |
can just produce a large amount of "correct" entries, e.g. |
| 21 |
|
| 22 |
mutt -> Mutt |
| 23 |
exim -> Exim |
| 24 |
|
| 25 |
And even not entirely correct, but still better: |
| 26 |
libreoffice-writer -> Libreoffice Writer |
| 27 |
|
| 28 |
Currently this is not possible (when Manifest is signed), since |
| 29 |
metadata.xml is included in the Manifest. However the thin manifest |
| 30 |
approach might allow something like this. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Fabian Groffen |
| 35 |
Gentoo on a different level |
Archives