public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Stiefelmaier <mail@stiefelweb.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Improved ebuild information
Date: Sat, 01 Oct 2005 22:19:39 +0200	[thread overview]
Message-ID: <433EEF5B.1040102@stiefelweb.de> (raw)

Hi!

I just opened this in gentoo-portage-dev, but Jason Stubbs told me my 
ideas are either bad or belong to THIS list, so i try my luck again...

I'd like to have a functionality that prints out what the useflags of a 
ebuild are good for. Some are obvious, others are not. Example:
The useflag "xprint" sounds like printing support, but doesn't tell if 
you need it if you use cups or the kde-printing system or... whatever.
Jason stated:

Take the USE flag "perl", for example. It has the description "Adds 
support/bindings for the Perl language." but for mysql setting it enables the 
installation of some support scripts that just happen to be written in perl.


Another thing is, that i'd like to get some additional information on 
some ebuilds.
Like HOWTOs, known issues, configuration help, related ebuilds (not 
dependant but useful together)
In my opinion, the easiest way would be a wiki.
Ebuilds could contain an additional field "EBUILDNOTES" or the like, 
providing the URL.
An even more simple way would be to have portage tools (eix, emerge) 
print an automatically generated link like
http://www.gentoo-wiki.com/Ebuild:www-client/mozilla-firefox
as mediawiki pages always have a discussion page attached, this could be 
used to get in touch with the maintainers of that package. (Only if they 
want that. This could be noted on the page)

thanks for reading and answering :)

Caliga
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2005-10-01 20:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 20:19 Daniel Stiefelmaier [this message]
2005-10-01 20:22 ` [gentoo-dev] Improved ebuild information Ciaran McCreesh
2005-10-02  0:10   ` Daniel Stiefelmaier
2005-10-02  6:06     ` Chris Gianelloni
2005-10-05 18:03   ` Martin Schlemmer
2005-10-05 18:34     ` Ciaran McCreesh
2005-10-05 21:13     ` [gentoo-dev] " R Hill
2005-10-10 12:53       ` Chris Gianelloni
2005-10-10 17:36         ` Bruno
2005-10-10 19:02           ` Apreche
2005-10-10 19:23         ` R Hill
2005-10-10 19:56           ` Thomas de Grenier de Latour
2005-10-01 20:25 ` [gentoo-dev] " Simon Stelling
2005-10-02  0:46   ` Daniel Stiefelmaier
2005-10-02  2:35     ` Alec Warner

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=433EEF5B.1040102@stiefelweb.de \
    --to=mail@stiefelweb.de \
    --cc=gentoo-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