On 17 July 2013 15:03, Bruce Hill <da...@happypenguincomputers.com> wrote:
> On Wed, Jul 17, 2013 at 02:18:22PM +0200, András Csányi wrote:
>> On 17 July 2013 13:59, Bruce Hill <da...@happypenguincomputers.com> wrote:
>> > On Wed, Jul 17, 2013 at 10:04:12AM +0200, András Csányi wrote:
>> >> >
>> >> > mingdao@jeremiah ~ $ grep plugdev 
>> >> > /usr/portage/net-misc/wicd/wicd-1.7.2.4-r*
>> >> > mingdao@jeremiah ~ $ grep users 
>> >> > /usr/portage/net-misc/wicd/wicd-1.7.2.4-r*
>> >> > /usr/portage/net-misc/wicd/wicd-1.7.2.4-r2.ebuild:              ewarn 
>> >> > "Wicd-1.6 and newer requires your user to be in the 'users' group. If"
>> >> > /usr/portage/net-misc/wicd/wicd-1.7.2.4-r3.ebuild:              ewarn 
>> >> > "Wicd-1.6 and newer requires your user to be in the 'users' group. If"
>> >>
>> >> Ok. How is possible to get the post-install message of an ebuild
>> >> without re-emerge the package neither opening the log file? The man
>> >> page of emerge cannot say anything about it.
>> >
>> > Read the pkg_postinst portion of the ebuild.
>>
>> Great!
>>
>> > If you have installed app-portage/elogv issue "elogv" and find the desired
>> > package.
>>
>> Thanks, I'll check it!
>>
>> > Two quick ways off the top of my head after the first cup of coffee. ;)
>>
>> The magic is coming from coffee, I know! :)
>
> Since reading the ebuild is not the _friendly_ way to get this information,
> let me help you install the software to make this easy...
>
> emerge -ajv app-portage/elogv (ncurses, which is text with colors)
> or
> emerge -ajv app-portage/elogviewer (GTK+ based utility, perhaps with GUI)
>
> Now add these lines to /etc/portage/make.conf (/etc/make.conf on old systems)
>
> PORTAGE_ELOG_SYSTEM="save"
> PORTAGE_ELOG_CLASSES="warn error info log qa"
>
> Then create this directory as root with this command:
>
> mkdir -p /var/log/portage/elog
>
> Then as root add your normal user to the portage group with this command:
>
> gpasswd -a <username> portage (replace <username> with your normal user's name
> and do not use the < >
>
> Then issue:
>
> newgrp
>
> as that user or logout of Linux and log back in (you do _not_ need to reboot).
>
> Then you can issue "elogv" or start elogviewer from the desktop entry and read
> the logs of your files.
>
> Hope this helps.
>
> Happy Gentooing!

Thanks for the help! This solution gives me what I want.

--
--  Csanyi Andras (Sayusi Ando)  -- http://sayusi.hu --
http://facebook.com/andras.csanyi
--  ""Trust in God and keep your gunpowder dry!" - Cromwell

Reply via email to