1 |
This comes from the following gentoo-dev thread: |
2 |
http://www.gossamer-threads.com/lists/gentoo/dev/264888 |
3 |
|
4 |
Its usage will lead to the installation of a CONFIGURATION file |
5 |
under /usr/share/doc/${PF} and show of elog messages with its content |
6 |
first time package is installed, relying in doc file for future |
7 |
installations or people simply going there to review configuration tips. |
8 |
|
9 |
I also attach acpid ebuild as example. |
10 |
|
11 |
Currently I have doubts about how to handle formatting, it is now using |
12 |
"fmt" as kernel-2.eclass to format it and, then, you can set: |
13 |
CONFIGURATION_INSTRUCTIONS=" |
14 |
You may wish to read the Gentoo Linux Power Management Guide, |
15 |
which can be found online at: |
16 |
http://www.gentoo.org/doc/en/power-management-guide.xml" |
17 |
|
18 |
and it will be properly formatted at the end. The problem is that I find |
19 |
no way to force a jump to a new line (for example if somebody want to |
20 |
show a command to run in a new line). |
21 |
|
22 |
Other option would be to simply add quotes to: |
23 |
echo ${CONFIGURATION_INSTRUCTIONS} |
24 |
|
25 |
and drop "fmt" usage. |
26 |
|
27 |
It will respect formatting specified in ebuild, but this needs to be |
28 |
taken into account as, for example, acpid ebuild used as example should |
29 |
be changed to use: |
30 |
CONFIGURATION_INSTRUCTIONS="You may wish to read the Gentoo Linux Power |
31 |
Management Guide, |
32 |
which can be found online at: |
33 |
http://www.gentoo.org/doc/en/power-management-guide.xml" |
34 |
|
35 |
or people will get an empty line at the top of the messages. |
36 |
|
37 |
Maybe an option to toggle fmt/formatting usage could be used, but I am |
38 |
unsure about how to handle it at eclass level in a "short" way (I could |
39 |
add some "ifs" running either variant (with quotes or without them and |
40 |
fmt usage), but not sure if a shorter way could be used) |