When I do an emerge -pvuDN world, I would really love to be able to see all of the einfo messages that would show when an emerge is performed. See this forum thread for discussion, as well as a working script that implements this functionality: http://forums.gentoo.org/viewtopic.php?p=5930125#5930125 Reproducible: Always Steps to Reproduce: 1. emerge -pvuDN world 2. note no einfo messages are output Actual Results: No einfo messages are seen during a --pretend emerge. Expected Results: I'd like to see the einfo messages for eack package during a --pretend emerge. Maybe a new -I (for info/eifno)? (I don't think it is used for anything right now) So: emerge -pvuIDN world would work the same as it does now, except under eack package I would see all einfo messages that would be output after a successful emerge. Thanks for Gentoo!
I really don't think this one will ever happen. A quick glance at the script tells me that it's just using grep to scrape out the various warnings from the ebuild. This doesn't take into account eclasses, conditionals in the ebuild, or do variable interpolation. It's not really even possible to fix this script, since the only way to *properly* get all of those messages is to *execute* the ebuild, which defeats the entire purpose.
I think what you want some more like a glep 42 news item: http://www.gentoo.org/proj/en/glep/glep-0042.html The elog functions just aren't designed for this type of use.
> A quick glance at the script tells me that it's just using grep to > scrape out the various warnings from the ebuild. This doesn't take > into account eclasses, conditionals in the ebuild, or do variable > interpolation. Ok, so its not perfect... but if there is an ewarn message informing the user of major breakage in certain cases, wouldn't it be 'a good thing' to see that/those message(s) during a --pretend emerge, instead of after the fact? Add a disclaimer if necessary, but some warning/info is better than none, right? Case in point, the minor update to mailman between 2.1.9-r1 and 2.1.9-r2, that changed the locations of the mailman files causing mailman to stop functioning. Alternatively, what is the best way - barring lots of hit/miss googling - to try to gauge the likelihood of any given update breaking something on my system, or requiring a lot of work to 'fix', due to some major change any given new ebuild/update introduces with respect to previous ebuilds?
I at first thought that this was sort of silly. But while testing it is usefull particularly if you update at least weekly or bi-weekly. I wish I had had this a couple weeks ago when baselayout2 and rc-conf updates had rolled through. I would have delayed till the weekend. Should this become a portage switch no. But added to "equery" or "q" yes. Maybe a stand alone like "euse". I have sped it up by 20% by putting the output into a file and then testing if file is zero sized. But its still slow.
I do update regularly... I --sync every day, then make note of any updates available, and wait a while (week, sometimes 2 or 3 if it is a critical package) to make sure there are no major issues that are quickly found/fixed. It would be fine with me if this was done via some other tool like equery, portage just seemed like a natural choice. Thanks for listening...
(In reply to comment #4) > Should this become a portage switch no. But added to "equery" or "q" yes. Maybe > a stand alone like "euse". You can file a new bug to have something like this included in equery (assign to tools-portage). As said in comment #2, it glep42 is a closer match for what you are trying to do. You may want consider adding some sort of extension to glep42 if it doesn't already meet your needs. You can file a bug for that and assign it to pms-bugs.
New Bug filed: http://bugs.gentoo.org/show_bug.cgi?id=281453 I read GLEP 42... looks promising, but what is the status? It was posted in October of 2005, and last updated in May of 2007...
(In reply to comment #7) > I read GLEP 42... looks promising, but what is the status? It was posted in > October of 2005, and last updated in May of 2007... It's being used now. You can see existing news items in /usr/portage/metadata/news/.
? I just looked, and there's nothing in there about any of the current update candidates... Here's the contents of my /usr/portage/metadata/news/: myhost news # ls -al total 5 drwxr-xr-x 9 root root 384 2009-08-14 06:11 . drwxr-xr-x 6 portage portage 272 2009-08-14 06:30 .. drwxr-xr-x 2 root root 96 2007-05-07 17:07 2007-05-04-paludis-0.24 drwxr-xr-x 2 root root 96 2009-01-08 18:09 2009-01-04-sparc-multilib drwxr-xr-x 2 root root 136 2009-04-05 16:13 2009-04-06-tetex drwxr-xr-x 2 root root 152 2009-04-05 16:13 2009-04-06-x_server-1_5 drwxr-xr-x 2 root root 176 2009-04-19 16:40 2009-04-18-java-config-wrapper-0.16 drwxr-xr-x 2 root root 528 2009-07-02 20:14 2009-07-02-kdeprefix+monolithics drwxr-xr-x 2 root root 152 2009-08-08 06:41 2009-07-12-xorg-74-alpha -rw-r--r-- 1 root root 32 2009-08-14 06:11 timestamp.chk myhost news # Currently, these updates are available for my system: myhost ~ # emerge -pvuDN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] virtual/perl-Package-Constants-0.01 0 kB [0] [ebuild U ] dev-libs/apr-1.3.8 [1.3.5] USE="urandom -debug -doc -older-kernels-compatibility%" 1,138 kB [0] [ebuild U ] app-editors/nano-2.1.9 [2.1.7-r1] USE="ncurses nls unicode -debug -justify -minimal -slang -spell" 1,450 kB [0] [ebuild NS ] dev-lang/python-2.6.2-r1 [2.5.4-r3] USE="berkdb gdbm ipv6 ncurses readline ssl threads xml -build -doc -examples -sqlite -tk -ucs2 -wininst" 10,905 kB [0] [ebuild U ] app-admin/python-updater-0.7 [0.5] 7 kB [0] [ebuild U ] net-misc/neon-0.28.5 [0.28.4] USE="nls ssl zlib -doc -expat -gnutls -kerberos -pkcs11 -socks5" LINGUAS="-cs -de -fr -ja -nn -pl -ru -tr -zh_CN" 759 kB [0] [ebuild NS ] sys-kernel/gentoo-sources-2.6.30-r4 [2.6.23-r9, 2.6.25-r7, 2.6.27-r8, 2.6.28-r5, 2.6.29-r5] USE="-build -symlink" 58,119 kB [0] [ebuild U ] dev-libs/apr-util-1.3.9 [1.3.7] USE="berkdb gdbm ldap mysql -doc -freetds -odbc -postgres -sqlite -sqlite3" 773 kB [0] [ebuild U ] net-mail/dovecot-1.2.3 [1.2.2] USE="berkdb doc ipv6 ldap managesieve mysql pam sieve ssl -caps -debug -kerberos -mbox -postgres -sqlite3 -suid -vpopmail" 3,900 kB [?=>1] [ebuild U ] sys-power/apcupsd-3.14.6 [3.14.5-r2] USE="nls snmp usb -cgi -gnome (-doc%)" 4,170 kB [0] [ebuild U ] dev-util/subversion-1.6.4 [1.6.3] USE="apache2 berkdb dso nls perl python sasl webdav-neon -bash-completion -ctypes-python -debug -doc -emacs -extras -gnome-keyring -java -ruby -test -vim-syntax -webdav-serf" 5,356 kB [0] [ebuild U ] net-mail/mailman-2.1.12 [2.1.11] 7,823 kB [0] Total: 12 packages (9 upgrades, 1 new, 2 in new slots), Size of downloads: 94,395 kB Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage/layman/whyscream [?] indicates that the source repository could not be determined myhost ~ #
