From: Svyatogor <svyatogor@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Readme files for portage (was: A nice idea to improve portage)
Date: Wed, 11 Jun 2003 11:52:14 +0000 [thread overview]
Message-ID: <20030611115214.4b3e2552.svyatogor@gentoo.org> (raw)
In-Reply-To: <34221.10.0.0.1.1055259612.squirrel@mooktaking.homeip.net>
I think it's a greаt idea. Unfortunately most discussion till now was around outputing
the the info to some log and so on. However the suggestion (which I was going to
make anyway) is much broader. The only pease of information portage helds about
every package is a short description line.
That's ok, if you know what the package does. Know imagine a situation when you
do emerge --pretend something and you get a list packages, some of which you have
no idea about. It would be very useful if you could read a readme file for them to see
what they are actually doing.
Having a readme would also be very useful in many other cases, when you want to get
some info on the package, without going to their web site.
On Tue, 10 Jun 2003 16:40:12 +0100 (BST)
"MooktaKiNG" <Mooktakim@hotmail.com> wrote:
> I think it would be better if portage included a README file for
> each ebuild.
>
> This i belive is very important becuase gentoo is a bit different
> from a normal linux.
>
> Like when installing a mod_php you run the command:
>
> ebuild .../mod_php config
>
> after installtion.
>
> See when i installed this first i had know idea.
>
> I know i know. there are some text at the end of the emerge that
> says what you should do.
>
> But when your doind multiple emerge's one after the other and you
> leave gentoo todo its thing. You don't see the text.
>
> So if there was a nice README file that explain the 'extra' setting
> needed on each dir in portage then it would make things a LOT easier
> and would be very helpful.
>
> If this already exists please ignore this email.
>
> -------------------------------------------------
> Please wait while you are redirected to my signature......
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
Sergey Kuleshov <svyatogor@gentoo.org>
Let the Force be with us!
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-11 9:02 UTC|newest]
Thread overview: 18+ 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
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 ` Svyatogor [this message]
2003-06-11 10:37 ` [gentoo-dev] Readme files for portage (was: A nice idea to improve portage) 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
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=20030611115214.4b3e2552.svyatogor@gentoo.org \
--to=svyatogor@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