On Sun, 14 Sep 2008 09:35:06 -0400, Tom \"spot\" Callaway wrote:
On Sun, 2008-09-14 at 10:36 +0200, Thorsten Leemhuis wrote:
> Yes, I know, enlightenment is designed for small machines and quite
> on them. But those things I quoted and other sections in the
> sound more like advertising than a proper description. Up to a specific
> point that's okay IMHO, but here the packager IMHO shoot way over the
Wow. That is indeed too much information. :) I'm not sure how we should
"guideline" that, other than something like:
== Descriptions ==
Your package description should contain useful data about the package,
and answer the question "what is this and what does it do?". In general,
the description should not exceed 10 lines or so. Try not to put too
much here, this isn't an epic novel, it's just a package description.
Also, there is no real need to "advertise" the package here, so
statements like "this is the best perl module that has ever been created
by humans", while possibly accurate, are not terribly useful in
answering the question "what is this and what does it do?".
I think these types of "advertising" and/or packager's notes are better
put into /usr/share/doc/package/README.RPM or similar. Maybe just an
additional sentence that packager's can stick extra additional info
there. Packagers already do this.