From: Daniel Stiefelmaier <mail@stiefelweb.de>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Improved user information and communication
Date: Sat, 01 Oct 2005 07:01:58 +0200 [thread overview]
Message-ID: <433E1846.1090106@stiefelweb.de> (raw)
Hi!
I'd like to introduce two ideas i had to improve portage.
sometimes i'd like to know something more about a package before i
emerge it.
1. release notes. (for the ebuild, not the application)
as a release notes file exists, a parameter could be used to show the
most recent entry.
maybe this fits "eix" better than "emerge"
2. advanced package info
most important here is an explanation of the available use flags. i know
there is a list of most flags (http://www.gentoo.org/dyn/use-index.xml)
but it is incomplete and doesnt explain some flags well. some have
different behaviour in different packages.
some flags are self-explanatory, but some are not. for example, the
"xprint" comment should say, that this is not necessary to print, and
under what circumstances it is needed.
also, the advanced could provide
- links to howto's (like configuring apache)
- list packages that are of use for this (plugins or utilized apps like
cervisia that integrates in quanta plus)
- tell how to contact the ebuild maintainer
that led my to another idea: a wiki for all ebuilds in portage.
all the information could then be in the wiki, and eix/emerge just print
the wiki-link.
i'd suggest mediawiki, as it has a discussion page attached.
maybe the wiki itself can only be changed by developers, and feedback is
given on the discussion page.
just some ideas, maybe needing some development, i hope you find them
useful. :)
greets, Caliga
--
gentoo-portage-dev@gentoo.org mailing list
next reply other threads:[~2005-10-01 4:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 5:01 Daniel Stiefelmaier [this message]
2005-10-01 5:17 ` [gentoo-portage-dev] Improved user information and communication Jason Stubbs
2005-10-01 16:08 ` Daniel Stiefelmaier
2005-10-01 17:04 ` Jason Stubbs
2005-10-01 19:41 ` Daniel Stiefelmaier
2005-10-01 20:07 ` Simon Stelling
2005-10-01 21:57 ` Daniel Stiefelmaier
2005-10-01 22:25 ` Brian Harring
2005-10-02 2:54 ` Daniel Stiefelmaier
2005-10-02 11:45 ` Simon Stelling
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=433E1846.1090106@stiefelweb.de \
--to=mail@stiefelweb.de \
--cc=gentoo-portage-dev@lists.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