Please, take a look at the following output: localhost libnotify # ebuild libnotify-0.4.5.ebuild merge Disabling noauto in features... merge disables it. (qmerge doesn't) [snipping checksums since they are [ ok ] ] >>> Checking libnotify-0.4.5.tar.gz's mtime... >>> WORKDIR is up-to-date, keeping... >>> It appears that 'libnotify-0.4.5' is already compiled; skipping. >>> Remove '/vt/portage/tmp/portage/x11-libs/libnotify-0.4.5/.compiled' to force compilation. >>> Test phase [not enabled]: x11-libs/libnotify-0.4.5 >>> Install libnotify-0.4.5 into /vt/portage/tmp/portage/x11-libs/libnotify-0.4.5/image/ category x11-libs [snip useful output] >>> Completed installing libnotify-0.4.5 into /vt/portage/tmp/portage/x11-libs/libnotify-0.4.5/image/ strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/bin/notify-send usr/lib64/libnotify.so.1.1.3 usr/lib64/libnotify.a removing executable bit: usr/lib64/libnotify.la localhost libnotify # Between "removing executable bit: usr/lib64/libnotify.la" and shell "localhost libnotify # " there is no output although package was installed.
I thought this was a feature.
Since bug #186842, the previous "quiet" behavior is default. The emerge --verbose option triggers the verbose output. The ebuild command does not currently have such an option, but we can add it.
Probably another way to solve this bug is to enable verbose for ebuild command always. I think if user uses ebuild command he already touches enough low level to see everything happening there.
Created attachment 177175 [details, diff] display files during merge by default (In reply to comment #3) > Probably another way to solve this bug is to enable verbose for ebuild command > always. I think if user uses ebuild command he already touches enough low level > to see everything happening there. Seems reasonable. Serkan, do you want a --quiet option to disable this?
(In reply to comment #4) > Created an attachment (id=177175) [edit] > display files during merge by default > > (In reply to comment #3) > > Probably another way to solve this bug is to enable verbose for ebuild command > > always. I think if user uses ebuild command he already touches enough low level > > to see everything happening there. > > Seems reasonable. Serkan, do you want a --quiet option to disable this? > I have no preference. Thanks.
This is fixed in 2.1.6.5 and 2.2_rc21.