From: Simon Stelling <blubb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Improved ebuild information
Date: Sat, 01 Oct 2005 22:25:12 +0200 [thread overview]
Message-ID: <433EF0A8.6080700@gentoo.org> (raw)
In-Reply-To: <433EEF5B.1040102@stiefelweb.de>
Hi,
Daniel Stiefelmaier wrote:
> In my opinion, the easiest way would be a wiki.
Indeed. But why do you need to modify all the ebuilds?
> 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)
Wikis are very popular, but they aren't the solution to every problem in the
world. If you want to contact the maintainer, write a mail, use IRC, or assign
bugs to them, but why do we need another (communication) channel?
It'd be great if you could animate people to concentrate useful information
about a package in a certain place, but that's really not the job of an ebuild
or portage.
Regards,
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
blubb@gentoo.org
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-01 20:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 20:19 [gentoo-dev] Improved ebuild information Daniel Stiefelmaier
2005-10-01 20:22 ` 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 ` Simon Stelling [this message]
2005-10-02 0:46 ` [gentoo-dev] " 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=433EF0A8.6080700@gentoo.org \
--to=blubb@gentoo.org \
--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