| 1 |
On Tuesday 13 April 2004 10:25 am, Mark Guertin wrote: |
| 2 |
> Most times you have to either a) log the entire build and go through it |
| 3 |
> by hand to figure out if there was crucial info that you missed or b) |
| 4 |
> go back after the fact and manually look at any ebuilds that were |
| 5 |
> installed to see if there are in fact ewarn's or einfo's in them. |
| 6 |
|
| 7 |
negative |
| 8 |
set PORT_LOGDIR in make.conf and then watch it be populated by |
| 9 |
einfo/ewarn/etc... |
| 10 |
i dont think it's an ideal solution but it's a *much* better solution than |
| 11 |
what you have above ... if perhaps portage would just cat all these files |
| 12 |
together and pipe it into $PAGER after the entire `emerge` is done, that'd be |
| 13 |
a *huge* gain ... |
| 14 |
|
| 15 |
for example, today i emerged quake2-icculus: |
| 16 |
$ less /var/log/portage/11126-quake2-icculus-0.15-r1.log |
| 17 |
prerm |
| 18 |
postrm |
| 19 |
postinst |
| 20 |
* Remember, in order to play games, you have to |
| 21 |
* be in the 'games' group. |
| 22 |
|
| 23 |
* See the usermod(8) manpage for more information. |
| 24 |
|
| 25 |
* Go read /usr/share/doc/quake2-icculus-0.15-r1/README-postinstall.gz right |
| 26 |
now! |
| 27 |
* It's important- This install is just the engine, you still need |
| 28 |
* the data paks. Go read. |
| 29 |
unpack |
| 30 |
>>> Unpacking source... |
| 31 |
>>> Unpacking quake2-r0.15.tar.gz |
| 32 |
to /var/tmp/portage/quake2-icculus-0.15-r1/work |
| 33 |
* Applying 0.15-Makefile-noopts.patch... [ ok ] |
| 34 |
* Applying 0.15-Makefile-optflags.patch... [ ok ] |
| 35 |
* Applying 0.15-gentoo-path.patch... [ ok ] |
| 36 |
>>> Source unpacked. |
| 37 |
-mike |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-security@g.o mailing list |
Archives