1 |
Hi folks, |
2 |
|
3 |
|
4 |
both in #gentoo and more importantly in bug reports, people are often |
5 |
asked to provide their `emerge --info', which gives a quick and |
6 |
very useful overview of the most important bits found on the system that |
7 |
wants support or (allegedly) exhibits a bug. Based on that information |
8 |
it is usually very easy to determine whether an issue arose because of, |
9 |
say, a problematic combination of packages, a configuration error or |
10 |
some unsupported compiler features. |
11 |
|
12 |
Paludis users often seem to think that `paludis --info' and `emerge |
13 |
--info' are interchangeable, whereas a quick inspection reveals to |
14 |
even the most casual user that the former only intends to inform about |
15 |
paludis' own compile time and run time configuration, whereas the |
16 |
latter includes information about a number of critical system |
17 |
packages, the global USE and USE_EXPAND variables and GENTOO_MIRRORS |
18 |
variable, to name a few. |
19 |
|
20 |
In short, `paludis --info' is not a replacement, and when `emerge |
21 |
--info' is asked for in a bug report, post *that*. There are many |
22 |
examples of what should be included out here, so if you can't or won't |
23 |
use emerge, then you'll have to copy the information manually. |
24 |
Remarking that you "don't use emerge" is not a valid reason not to post |
25 |
it - post both `(emerge|paludis) --info' if you must - having both |
26 |
there will help greatly and is necessary for the time being[1]. |
27 |
|
28 |
|
29 |
Kind regards, |
30 |
jer |
31 |
|
32 |
|
33 |
[1] Future development could see the release of a unified, fully |
34 |
supported `$PM--info' feature or perhaps a separate tool, and |
35 |
this side issue is most likely off topic on gentoo-dev@. |