How make emerge ignore packages basing on date?

[ayvango]

I tried to to emerge -e --keep-going world, but it failed half-way with a package and couldn't keep-going since it detected some sort of conflict. That is not the first time when keep-going fell down on the job, but normally I just repeat the last command and portage manages to continue the build. In cast of -e entire world rebuilding it is really exhausting to rebuild world many times.

Is it possible to make emerge look into the date on /var/db/pkg and skip package building if it is newer then supplied? If there is no such built-in option, could there be some dirty hacks?

[freke]

Doesn't

Code: Select all

emerge --resume

work for you?

[ayvango]

nope. It shows the same dependency resolution error as keep-going.

Code: Select all

 * The resume list contains packages that are either masked or have
 * unsatisfied dependencies. Please restart/continue the operation
 * manually, or use --skipfirst to skip the first package in the list and
 * any other packages that may be masked or have missing dependencies.

[John R. Graham]

"emerge --emptytree @world" will generally work reliably if your system is up to date and conflict free before you run it. That means you need to run

Code: Select all

emerge --update --deep --changed-use --with-bdeps=y @world

and also follow any recommended preserved rebuild and --depclean instructions. Once your system is fully up to date and clean, try the --emptytree emerge again.

If this is not true for you, then actual error messages will help.

- John

[ayvango]

"emerge --emptytree @world" will generally work reliably if your system is up to date and conflict free before you run it.

Well, in my case error were caused by side info unavailable for the portage system.

sci-libs/hdf5 was rebuilding to the same version and use flags as it were previously installed, but failed.
after that I manually rebuild sys-claster/openmpi to the same version and use flags as it were previously installed
after that sci-liubs/hdf5 successfully emerged

ergo, portage could not catch all side-effects presented by packages. I believe this is the reason for the emptytree option existence: to rebuild all packages and redo all side effects that portage could not handle otherwise. This is exactly my case: I'm performing emerge -e as it was recommended for the profile update.

you have too many faith in portage. Actually it is not so good abstraction and leaks everywhere.

I expect that fast-patching portage to ignore packages would cost less time than rebuilding entire world many times. Now I'm skimming through sources to find function that calls actual package build and patch it. Could you point me any direction for my search?

[Hu]

If you are that determined to bypass the package manager, would it not be simpler to enumerate all packages that need to be rebuilt, then use emerge --oneshot $(< enumerated-package-list )? This will ask Portage to rebuild all of them, and not add them to world. It will still respect dependency ordering, and it lets you include or exclude packages at will.

[Ant P.]

List of all packages that were last emerged at or before another given package:

Code: Select all

PKG=$(portageq best_version / sys-libs/zlib) # example
find /var/db/pkg/ -mindepth 2 -maxdepth 2 -! -newer /var/db/pkg/$PKG -printf '=%P\n'

As always, this information is provided without warranty.

[ayvango]

I have similar thoughts. Using find is not a problem, but how could I hack emerge to take that list into consideration. The ideal case it to hook function that does actual package building and omit it if some conditions is met. I looked inside the portage sources, but give up to locate expected procedure. Portage is too asynchronous and OOP to navigate through it with ease.

[Hu]

Why are you hacking emerge at all? I told you how to invoke emerge with the package list in a file named enumerated-package-list, and Ant P. showed you how to generate the package list. No code changes are required. Use his command to generate a list of packages. Review it. If it satisfies your requirements, run emerge --oneshot and pass as command line arguments the list generated by his command.

[ayvango]

Ant. P. generates already installed list. But I'd like to get resolved list in the correct order from the emerge.

But in any case I get obsessed with strange ideas, when solution could be rather simple. Just make emerge --pretend generate list of packages and use bash for loop to install each packet in given order.

[Genone]

https://dev.gentoo.org/~zmedico/portage ... 03s12.html