View previous topic :: View next topic |
Author |
Message |
trckry n00b
Joined: 27 Apr 2006 Posts: 7
|
Posted: Tue Aug 22, 2006 3:15 pm Post subject: Why is emerge.log location not configurable? |
|
|
I was playing around with how my /var/log looked today,
trying to clean it up and organize it more to my liking. The
only hang up was emerge.log, which I found out is statically
set in /usr/bin/emerge on line 236.
Code: | file_path = "/var/log/emerge.log" |
Now, it's trivial to change that to what I want it to be, but I was
just wondering if there was any reason it wasn't configurable? |
|
Back to top |
|
|
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9532 Location: beyond the rim
|
Posted: Tue Aug 22, 2006 5:43 pm Post subject: |
|
|
There are quite a number of tools that currently rely on it being where it is. Before you can make it configurable you'd have to make sure all these tools can handle that which requires quite a bit of effort and coordination (not all of these tools are developed by Gentoo). |
|
Back to top |
|
|
trckry n00b
Joined: 27 Apr 2006 Posts: 7
|
Posted: Tue Aug 22, 2006 6:31 pm Post subject: |
|
|
It makes a lot of sense not to break existing software if at all possible. It would help if there was a list somewhere of those software packages.
I did an eix search and the only thing that came up was genlop. I checked Google too and the only other thing I got a hit on besides genlop were some home brewed, easily changed bash scripts.. and genlop is already setup to handle non default emerge.log locations, as well as multiple files and compression, in case you're rotating your files.
Can you think of any other tools that use it? Maybe not explicitly parsing it, but depending on it? |
|
Back to top |
|
|
trckry n00b
Joined: 27 Apr 2006 Posts: 7
|
Posted: Tue Aug 22, 2006 6:38 pm Post subject: |
|
|
Looking at some of the other logs, when parallel fetching is on, /var/log/emerge-fetch.log is also statically set. |
|
Back to top |
|
|
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9532 Location: beyond the rim
|
Posted: Tue Aug 22, 2006 8:58 pm Post subject: |
|
|
A (incomplete) list: genlop, splat, gentoo-stats (not in the tree yet), regenworld (from portage). Basically anything that needs a build history or buildtimes. |
|
Back to top |
|
|
limn l33t
Joined: 13 May 2005 Posts: 997
|
Posted: Tue Aug 22, 2006 9:35 pm Post subject: |
|
|
I have been considering that it would be convenient and consistent for /var/log/emerge.log to be prefixed with ROOT.
A variable to set its location seems a reasonable enhancement request. |
|
Back to top |
|
|
trckry n00b
Joined: 27 Apr 2006 Posts: 7
|
Posted: Tue Aug 22, 2006 11:03 pm Post subject: |
|
|
I agree with Limn, obviously . Of those you listed, splat is also configurable to look at any given file, and regenworld is provided by the portage package, so is in the control of the portage maintainers to change. gentoo-stats I don't have any information on since it's not in the tree yet.
Basically though, this is a rather esoteric setting. With sane defaults, i.e. keeping it where it is, all those packages would still work normally for the users that don't choose to use the setting. And for those that do, a quick shell alias would fix any of the packages that you listed for that user. |
|
Back to top |
|
|
trckry n00b
Joined: 27 Apr 2006 Posts: 7
|
|
Back to top |
|
|
xentric Guru
Joined: 16 Mar 2003 Posts: 410 Location: Netherlands
|
Posted: Sun Sep 03, 2006 12:16 pm Post subject: |
|
|
The new version of cfg-update (1.8.0-r4, not yet released!) will also use /var/log/emerge.log by default but if that file does not exist, cfg-update will ask the user to specify the location of the emerge.log in /etc/cfg-update.conf (EMERGELOG=/path/emerge.log)... So there should not be any problems with cfg-update! _________________ When all else fails, read the manual...
Registered Linux User #340626 |
|
Back to top |
|
|
|