1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
|
5 |
Ok really first off, I am not a gentoo developer, just to let you know :) |
6 |
|
7 |
First off, everything here is basically taken out of context from |
8 |
gentoo-portage-dev, so the only sane responses ( to this mail, not the |
9 |
other one, which was different ) are going to be from people who read both. |
10 |
> |
11 |
>>> In my opinion, the easiest way would be a wiki. |
12 |
>> |
13 |
>> |
14 |
>> |
15 |
>> Indeed. But why do you need to modify all the ebuilds? |
16 |
> |
17 |
> |
18 |
> do i have to? of course it is not necessary to modify 10k ebuilds in a |
19 |
> week. The line could be added on the next regular update. And as said |
20 |
> below, it could also be generated automatically by the tool that reads |
21 |
> the packages metadata. |
22 |
> |
23 |
|
24 |
Regardless of where this data is going, SOME{ONE,THING} has to compile |
25 |
it all. You spoke on the other ML of HOW-TO links and all manner of |
26 |
info. That info is great. The problem is convincing ebuild developers |
27 |
to compile the data in the first place, and keep it accurate. That is |
28 |
why we suggested you try your ideas here. Writing this stuff into a |
29 |
tool or patching portage is useless if no one compiles/updates this |
30 |
information. |
31 |
|
32 |
> All that has to be done is create a way to print the path to a wiki-page. |
33 |
> Maybe auto-created by eix. Or maybe a new tool named "einfo" that prints |
34 |
> the information included in metadata.xml. |
35 |
> |
36 |
> greets, |
37 |
> Caliga |
38 |
|
39 |
Case 1: Project specific things -> Homepage, guides, HOW-TO's |
40 |
I like what you are looking for, however I don't think it should be a |
41 |
Gentoo-specific project. If one was to make some sort of online |
42 |
repository of packages and associated helpful guides on using them, that |
43 |
would be cool. Even cooler would be if it stood alone from Gentoo ( not |
44 |
a gentoo-only project ). Then every distro could use it, along with |
45 |
most other UNIXes. |
46 |
|
47 |
Then you can make a command-line tool or whatnot to query the on-line |
48 |
database for the information you are looking for. |
49 |
|
50 |
In any case, I personally don't believe any of this belongs in portage, |
51 |
metadata.xml or wherever. Portage's job is to install packages. I |
52 |
don't think many people want tons of irrelevant data in the tree, most |
53 |
people have no problem using a search engine to find it anyway. |
54 |
|
55 |
Case 2: USE flag specific things. |
56 |
This is more tricky. In the current version of portage USE flags are |
57 |
the only way to enable things on a per-package basis. This gives us |
58 |
wonderful things like USE="debug" which is just ass-backwards. People |
59 |
use USE flags for things that in most cases aren't meant for USE flags |
60 |
or go against the global USE flag usage. |
61 |
|
62 |
You will get cases where USE flag usage is abnormal. In that case I'd |
63 |
file bugs against respective packages ( aka, when a global USE flag is |
64 |
used in a way that doesn't jive with that USE flag's global usage. ). |
65 |
If you want to query what flags do, there are utilities for that ( ufed, |
66 |
pyfed? ). If you want more descriptive usage of USE flags, bug the |
67 |
ebuild developers to add more text to the appropriate file, or read the |
68 |
ebuild. |
69 |
|
70 |
Case 3: Update Paths |
71 |
For major packages Gentoo generally does a decent job providing upgrade |
72 |
documentation. Either the lead dev for that herd/project will write it |
73 |
up in their devspace, or put it somewhere. It's often printed at |
74 |
install time as well, and there are tools to catch all those handy |
75 |
messages :) |
76 |
However there are many smaller packages that don't get this kind of |
77 |
support and you are sometimes left fending for yourself a bit as to |
78 |
figuring stuff out, or the solution to your problem is printed at |
79 |
install time ( by install time, I mean post_inst() in portage terms ). |
80 |
I've already had that argument on this list though, and it basically |
81 |
came down to better gentoo commit messages and the fact that the gentoo |
82 |
developers are not responsible for keeping me informed about my packages |
83 |
and whether this upgrade breaks them. And honestly, I understand that. |
84 |
|
85 |
Part of the coolness/problem with gentoo is that you are basically left |
86 |
as your own system administration. This isn't redhat where you are |
87 |
handheld through everything. Many people get along that way on gentoo, |
88 |
stuff breaks, they reinstall, end of story. If you are upgrading |
89 |
package foo and you don't know if it's important or not, or if it will |
90 |
break your system you may want to go and check it out. What does foo |
91 |
do, what depends on foo ( equery and gentoolkit )? Check |
92 |
bugs.gentoo.org or foo's bugzilla for open bugs and check foo's |
93 |
Changelog ( the package changelog mind, not the gentoo changelog ). |
94 |
|
95 |
Good Luck, |
96 |
|
97 |
Alec Warner ( antarus ) |
98 |
-----BEGIN PGP SIGNATURE----- |
99 |
Version: GnuPG v1.4.1 (GNU/Linux) |
100 |
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
101 |
|
102 |
iQIVAwUBQz9HamzglR5RwbyYAQLiLw//epYhdGOnSM2KUC8hFRkVin4f+KDPNxf1 |
103 |
QvbbfX3gaEfryY2PymcjoOmfWYzySPD6SJhrETnscVMU3lSS26xFSuKdSP+T66rK |
104 |
a9zvO+JeVn+GDm+dyVLjZxtJTLcv23bCzwrS4EcNVpT33iV0OkYkKHIKPqcGh02O |
105 |
GxMmKi3SD5wz6mJYzm9tDAdCxsb7g3TaWJlpUm99wvkcf+JlZLSomz3odxCB7mh8 |
106 |
bQqcpyCyrpdpD/FnrE6GQ68NTg2Axfsck85SwcGdJAgwR7yi9pr3ZSKUZKe19AoY |
107 |
Fz/xQIKIXAlUzRHdAIP3k/nTWawXU0+pucsWJy6S84qsJ+1GIY2EwWU8wpd51llc |
108 |
k6vPTb+k7X9IGo2uNQvyqIIsHruw9Qi0ZiswF8r8d4gZarBBzaTixoK9ThGU/uvg |
109 |
zLdfYS+1VeIB/3F1MZ3DW4heVGPriZ9H+xxjG9seD5CbqsT2gIVGeyYVwkzx+8LT |
110 |
N6Pz6PiUb1OxZoXyOyLCneE/JsEN3UTFBgpbfqUb061N+0eTPyI+46juuF+N50cE |
111 |
g1fcDnvlGVOYvCGRbaursK2HNK/TqBcXoz0xMB10eJkuh+TX5triK6Xhgaxn51gc |
112 |
x1m2GzZ58K2th0xlsCw/0mk/kILvHYN9Sb8hk/cHEoHg2QnxrdyoPr9ecoG+StHM |
113 |
FgqIJvNeNxE= |
114 |
=9WY7 |
115 |
-----END PGP SIGNATURE----- |
116 |
-- |
117 |
gentoo-dev@g.o mailing list |