From: Frantz Dhin <fd@redspot.dk>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Horrible package descriptions
Date: 23 May 2003 04:04:55 +0200 [thread overview]
Message-ID: <1053655495.13745.4.camel@localhost> (raw)
In-Reply-To: <200305222102.37444.pauldv@gentoo.org>
On Thu, 2003-05-22 at 21:02, Paul de Vrieze wrote:
> My biggest point against long descriptions is the fact they need to be
> written. That is not such a big point if the users will do it. I do think
> though that a description file might be more appropriate than putting the
> long description in the ebuild. A package description should always be the
> same I feel, even over versions.
>
> Paul
I suppose other distributions such as Mandrake wont mind us borrowing
their usually nice descriptions?
I'm all for a long description, and I don't think it will take a lot of
resources to implement.
-F
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-23 2:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 18:12 [gentoo-dev] Horrible package descriptions Vadim
2003-05-22 18:23 ` oford
2003-05-22 18:31 ` Dhruba Bandopadhyay
2003-05-22 19:01 ` John Robinson
2003-05-22 19:07 ` Seemant Kulleen
2003-05-22 20:28 ` Spundun Bhatt
2003-05-22 18:34 ` Sven Vermeulen
2003-05-22 18:56 ` Dylan Carlson
2003-05-22 19:02 ` Paul de Vrieze
2003-05-22 19:11 ` Dylan Carlson
2003-05-22 19:17 ` Paul de Vrieze
2003-05-23 2:04 ` Frantz Dhin [this message]
2003-05-23 19:40 ` leon j. breedt
2003-05-22 20:59 ` Matt Tucker
2003-05-23 10:23 ` Sven Vermeulen
2003-05-22 19:17 ` Matthew Kennedy
2003-05-22 19:19 ` Matthew Kennedy
2003-05-22 19:34 ` Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:06 Vadim
2003-05-22 23:20 ` Ernst Herzberg
2003-05-23 2:55 ` John Nilsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1053655495.13745.4.camel@localhost \
--to=fd@redspot.dk \
--cc=gentoo-dev@gentoo.org \
--cc=pauldv@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox