ebuild reporting in /proc, Quing and emerge process control

[jago25_98]

Ebuild Process Reporting:

(I may try and script this with the time command but it probably won't mix well with python, I aplogise for not being fluent in python)

- log start time of ebuild

- log size of distfile being compiled (lines of code via sloccount or simply size of compilable files)

- log time of finished ebuild

=> use time taken and size of compile to generate ETA for next ebuild. It's only rough but remember: better than nothing. Report info in ambiguous manner.

^ All this needn't be don't by one person in one go! If you've a good idea on how to log the start time of ebuilds / emerges then go for it! Then someone else can take it to the next stage.

Alternatively! - Simply note how many make commands have been executed and how many need to be done before the emerge will be complete! This could then be improved by giving an indication of the size of files that have yet to be compiled.

Process Control and reporting:

- Que emerge requests and / or make command. Make this queing info available and user able to edit priority.

- Export new make commands to another MOSIX node.

Wish I could help. I'm going to try and script this but I have never programmed anything before!

Try to stay in touch, let us know what you achieve.

[pjp]

Moving from Portage & Programming to Gentoo Chat. Polls are better suited for a discussion forum.
_________________
Quis separabit? Quo animo?

[Dolio]

If possible, it'd probably be good to keep a record of lines of code compiled and the time taken (or time/lines and lines). Then with each ebuild you do, you could add to the average and make the person's time/line more and more 'accurate,' so eventually you'd zero in on the correct average.

Just a thought.
_________________
They don't have a good bathroom to do coke in.

[pjp]

I'm guessing there is no reasonable way to estimate how long compiling something will take. In the off chance that a feature like this is implemented, I would suggest something like:

• No need to get out of the chair, I'll be done shortly.
  
• Get a cup of your favorite beverage and have a chat with someone, this is going to take a while.
  
• Have you read the newspaper yet?
  
• You should consider compiling this overnight.
  
• You should take a vacation, I'll be done when you get back.

_________________
Quis separabit? Quo animo?

[ejdmoo]

Just have a benchmark by which to follow, and always keep it the same. The benchmark, however, should be based more on time than anything else. Then, you could learn about how long that benchmark is on your system. "This will take 1,655 widgets to complete." Then you would know, from comparison, how long that is for your setup.
_________________
Those are my two cents