From: Matthew Kennedy <mkennedy@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] A nice idea to improve portage
Date: Tue, 10 Jun 2003 11:07:44 -0500 [thread overview]
Message-ID: <87d6hlex0v.fsf@killr.ath.cx> (raw)
In-Reply-To: <34221.10.0.0.1.1055259612.squirrel@mooktaking.homeip.net> (MooktaKiNG's message of "Tue, 10 Jun 2003 16:40:12 +0100 (BST)")
"MooktaKiNG" <Mooktakim@hotmail.com> writes:
> I think it would be better if portage included a README file for
> each ebuild.
>
I think this is a good idea. Many ebuilds already include a
REAME.Gentoo which contains extra information. Its possible that
this is not used consistently though.
Matt
--
Matthew Kennedy
Gentoo Linux Developer
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-10 16:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 14:25 [gentoo-dev] ebuild question MAL
2003-06-10 15:40 ` [gentoo-dev] A nice idea to improve portage MooktaKiNG
2003-06-10 16:07 ` Matthew Kennedy [this message]
2003-06-10 18:05 ` John Robinson
2003-06-10 20:20 ` Philippe Lafoucrière
2003-06-11 3:18 ` Luke Graham
2003-06-11 5:10 ` Bill Kenworthy
2003-06-10 21:56 ` MooktaKiNG
2003-06-10 21:42 ` Zach Forrest
2003-06-10 23:26 ` Kumba
2003-06-11 11:52 ` [gentoo-dev] Readme files for portage (was: A nice idea to improve portage) Svyatogor
2003-06-11 10:37 ` MooktaKiNG
2003-06-11 10:10 ` Michael Cummings
2003-06-11 10:44 ` Paul de Vrieze
2003-06-11 13:24 ` [gentoo-dev] " D. Tuinstra
2003-06-11 15:47 ` oford
2003-06-11 17:06 ` [gentoo-dev] " MooktaKiNG
2003-06-12 11:34 ` [gentoo-dev] ebuild question Amiel Martin
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 18:16 [gentoo-dev] A nice idea to improve portage Balaji Srinivasan
2003-06-10 18:36 ` Marius Mauch
2003-06-10 18:46 ` John Robinson
2003-06-10 20:02 ` Todd Berman
[not found] ` <1055271494.8194.8.camel@devweb>
2003-06-10 20:11 ` John Robinson
2003-06-10 20:15 Balaji Srinivasan
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=87d6hlex0v.fsf@killr.ath.cx \
--to=mkennedy@gentoo.org \
--cc=gentoo-dev@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