| 1 |
On Mon, 2005-09-12 at 08:01 -0500, Brian Harring wrote: |
| 2 |
> On Mon, Sep 12, 2005 at 02:13:43PM +0200, Frank Schafer wrote: |
| 3 |
> > Hi, |
| 4 |
> > |
| 5 |
> > I fought with a stage1 install during this weekend. Today in the morning |
| 6 |
> > I succeeded. |
| 7 |
> > I had to move a lot in /var/log/portage. |
| 8 |
> > |
| 9 |
> > For the content of this directory I'd suggest the following: |
| 10 |
> > |
| 11 |
> > Remove the 4 digit number from the log file names. |
| 12 |
> They're relevant to portage stable; down the line it'll likely be |
| 13 |
> mtime based. |
| 14 |
> Right now that 4 digit number is an internal incrementing counter |
| 15 |
> that's tagged into the log file name. |
| 16 |
|
| 17 |
I realized that. My suggestion was to NOT tag it there. It is more |
| 18 |
annoying for the person who has to work with this directory. I know |
| 19 |
there are a lot of gensomething tools but they don't do anything else |
| 20 |
than duplicate the functionality of ``ls'' in this case. Leave it |
| 21 |
simple! |
| 22 |
|
| 23 |
> |
| 24 |
> > It is a good idea to have 2 files for each package. One with the output |
| 25 |
> > of make and one with the messages for the installer. Name the former |
| 26 |
> > package-version.log and the latter package-version.msg |
| 27 |
> |
| 28 |
> Doesn't work that way, and what you're after (restating your |
| 29 |
> 'installer' as enotice/ewarn/einfo) is elog, something that'll be in |
| 30 |
> the next major version. |
| 31 |
|
| 32 |
No, :D my installer is the person who installs the system :) |
| 33 |
|
| 34 |
> |
| 35 |
> You're seeing two logs due to the fact you have FEATURES="buildpkg" |
| 36 |
> on; effectively, portage build's the binpkg (log 1), then merges it |
| 37 |
> (log 2). This is inneficient though, since it builds up one $IMAGE |
| 38 |
> dir, binpkg's it, then dumps it to another dir and installs from that. |
| 39 |
> |
| 40 |
> That's an old annoyance that should die a miserable death soon enough. |
| 41 |
|
| 42 |
Please don't say that you plan to make the only sense-making messages to |
| 43 |
nearly dismiss within many mega log files :( |
| 44 |
|
| 45 |
Having a special function for logging (elog) is a good thing. This |
| 46 |
function could create the pkg.version.log (output of the build process - |
| 47 |
mostly make) and pkg.version.msg (the notes which some packages write |
| 48 |
out meant for people what to be aware of). Unfortunately I'm not so good |
| 49 |
in Python and don't have much time. So I can't involve in direct |
| 50 |
development. Maybe this will be better in half a year. |
| 51 |
|
| 52 |
> ~harring |
| 53 |
|
| 54 |
Regards |
| 55 |
Frank |
| 56 |
|
| 57 |
PS: That's not meant as critics - it's a suggestion (see the subject ;) |
| 58 |
-- |
| 59 |
gentoo-dev@g.o mailing list |
Archives