In my opinion, the easiest way would be a wiki.
Indeed. But why do you need to modify all the ebuilds?
do i have to? of course it is not necessary to modify 10k ebuilds in a
week. The line could be added on the next regular update. And as said
below, it could also be generated automatically by the tool that reads
the packages metadata.
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?
You're right, maybe that discussion thing is not so useful. The only
thing advantage i see is that the inhibition to participate is very low
for a wiki. I helped with inkscape.org and met people that never use
CVS, IRC, Jabber... Those can still write in the wiki. And still, if the
discussion page should not be used for feedback, maintainers could state
how they prefer to be contacted.
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.
That sounds like
"your target is good, your way may work, but your way is wrong. i don't
know the right way"
I just can't understand what is so wrong with providing metadata with a
package. what is metadat.xml then good for?
Above you said, it was good to have relevant information concentrated at
a specific place.
Just a half hour before you said, the defined way to get such
information is google.
Now, what? Google doesn't concentrate.
All that has to be done is create a way to print the path to a wiki-page.
Maybe auto-created by eix. Or maybe a new tool named "einfo" that prints
the information included in metadata.xml.
greets,
Caliga
--
[email protected] mailing list
