| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi guys, |
| 5 |
|
| 6 |
There are some things that I forgot to tell ya. |
| 7 |
|
| 8 |
I know that lots of you don't know "dpkg-reconfigure", well, it will |
| 9 |
write the /etc/whatever.conf file for you asking you in an interactive |
| 10 |
way what do you want to do. I'd compare it to some package's "ebuild |
| 11 |
/usr/portage/whatever/whatever-0.0.1.ebuild conf". |
| 12 |
|
| 13 |
I would add a mark for packages that can be configured, as there is a |
| 14 |
mark for UPDATE, NEW, RE-EMERGE, FETCH... I'd add another one like "C" |
| 15 |
for ebuilds that admit "conf" option. |
| 16 |
|
| 17 |
As someone said here before, EMERGE is a not interactive tool (if we |
| 18 |
don't take in count --ask), but in general it is not interactive. And we |
| 19 |
can assume that anybody stays in front of monitor all the emerge |
| 20 |
process, so I'd suggest to print information (or warning) messages in a |
| 21 |
more efficient way, for example: AT THE END OF THE EMERGE PROCESS, not |
| 22 |
at the end of each package emerge process. I think that |
| 23 |
PORTAGE_ELOG_CLASSES, PORTAGE_ELOG_SYSTEM and PORTAGE_ELOG_MAILURI is |
| 24 |
not so necessary if all messages are printed out at the end of the |
| 25 |
global emerge process. |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v1.4.4 (GNU/Linux) |
| 28 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 29 |
|
| 30 |
iD8DBQFEr6UAWFfYaTyFH8oRAisJAJ9rzuxt/wKJPAvXoCdU9d4JcCoIkACghuPf |
| 31 |
xEju9eUjrUPsOG7HMnM7F9A= |
| 32 |
=cqyw |
| 33 |
-----END PGP SIGNATURE----- |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives