Mailinglist Archive: yast-devel (26 mails)

< Previous Next >
[yast-devel] Displaying Package Descriptions
  • From: Karl Eichwalder <ke@xxxxxxx>
  • Date: Tue, 07 Sep 2010 13:48:57 +0200
  • Message-id: <shbp89wz86.fsf@xxxxxxxxxxxxxxx>
There seems to be doubt about displaying package descriptions. What do
we want to do with lists within a package description? For example, see
the squid3 package:

Squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP,
and more. It reduces bandwidth and improves response times by
caching and reusing frequently-requested web pages. Squid has
extensive access controls and makes a great server
accelerator. Squid 3.0 represents a major rewrite of Squid and has a
number of new features. The most important of these are: - Code
converted to C++, with significant internal restructuring and
rewrites. - ICAP implementation (RFC 3507 and www.icap-forum.org) -
Edge Side Includes (ESI) implementation (www.esi.org) Most
user-facing changes are reflected in squid.conf.


This is just running text, but the writer probably meant:

... Squid 3.0 represents a major rewrite of Squid and has a
number of new features. The most important of these are:

- Code converted to C++, with significant internal restructuring and
rewrites.
- ICAP implementation (RFC 3507 and www.icap-forum.org)
- Edge Side Includes (ESI) implementation (www.esi.org) Most
user-facing changes are reflected in squid.conf.

or something similar. In other packages, you will find stars (*) to
denote list items.

Do we still want to the "Authors" as part of the package description?

--
Karl Eichwalder
R&D / Documentation

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
Follow Ups