1 |
>> In my opinion, the easiest way would be a wiki. |
2 |
> |
3 |
> |
4 |
> Indeed. But why do you need to modify all the ebuilds? |
5 |
|
6 |
do i have to? of course it is not necessary to modify 10k ebuilds in a |
7 |
week. The line could be added on the next regular update. And as said |
8 |
below, it could also be generated automatically by the tool that reads |
9 |
the packages metadata. |
10 |
|
11 |
> Wikis are very popular, but they aren't the solution to every problem |
12 |
> in the world. If you want to contact the maintainer, write a mail, use |
13 |
> IRC, or assign bugs to them, but why do we need another |
14 |
> (communication) channel? |
15 |
|
16 |
You're right, maybe that discussion thing is not so useful. The only |
17 |
thing advantage i see is that the inhibition to participate is very low |
18 |
for a wiki. I helped with inkscape.org and met people that never use |
19 |
CVS, IRC, Jabber... Those can still write in the wiki. And still, if the |
20 |
discussion page should not be used for feedback, maintainers could state |
21 |
how they prefer to be contacted. |
22 |
|
23 |
> It'd be great if you could animate people to concentrate useful |
24 |
> information about a package in a certain place, but that's really not |
25 |
> the job of an ebuild or portage. |
26 |
|
27 |
That sounds like |
28 |
"your target is good, your way may work, but your way is wrong. i don't |
29 |
know the right way" |
30 |
|
31 |
I just can't understand what is so wrong with providing metadata with a |
32 |
package. what is metadat.xml then good for? |
33 |
|
34 |
Above you said, it was good to have relevant information concentrated at |
35 |
a specific place. |
36 |
Just a half hour before you said, the defined way to get such |
37 |
information is google. |
38 |
Now, what? Google doesn't concentrate. |
39 |
|
40 |
All that has to be done is create a way to print the path to a wiki-page. |
41 |
Maybe auto-created by eix. Or maybe a new tool named "einfo" that prints |
42 |
the information included in metadata.xml. |
43 |
|
44 |
greets, |
45 |
Caliga |
46 |
-- |
47 |
gentoo-dev@g.o mailing list |