[SOLVED] Keep gentoo-sources from updating

[hololeap]

I apologize if this has already been asked a million times, but I wasn't able to find an answer for my specific problem.

Basically, I want to keep Portage from upgrading sys-kernel/gentoo-sources when I do a "emerge -DNu --with-bdeps y world".

I have the following entry in my world file:

[nemectic]

[NeddySeagoon]

hololeap,

sys-kernel/gentoo-sources is slotted. Its one slot per vesrion so you can have many versions installed at the same time.
Your world file entry

[Logicien]

The linux-sources have an only but important internal USE flag: firmware. When the flag is active, if the linux-sources are updated, the linux-firmware package will be updated at the same time for the kernel and modules of the new version be able to access the appropriate firmware files who change from a kernel version to another.

I think it's a good idea to keep this virtual package install. Did you edit manually var/lib/portage/world? I have only the line

[TomWij]

-r1 is a revision bump fixing a common random hang as well as security fixes; if you don't want it, just mask it.

[hololeap]

Thanks for the responses.

My question is more theoretical and less pragmatic (I already know about the package.mask and --exclude options). What I don't understand is where the update is coming from. It would make sense if I had "sys-kernel/gentoo-sources" in my world file, as that would include any available version. But, since the world entry is one specific slot, it should only pull in ebuilds from that slot. The 3.10.7-r1 version is getting pulled in by virtual/linux-kernel, but that package's dependencies should be fulfilled by version 3.10.7 and I don't see why it wants a later version.

UPDATE:

I removed 3.10.7 and installed 3.10.9. Still, emerge is trying to pull in 3.10.7-r1. I'll investigate further, but this doesn't seem like ideal behavior. Virtual packages should only pull in packages if they are needed for a dependency and that dependency is currently unmet. Wasn't that what bug 370295 was all about?

[Budoka]

I placed the line

[TomWij]

[hololeap]

Actually it looks like the reason is that 3.10.9 has been taken out of portage tree.

So the question has boiled down to: Is there a way to make virtual packages "lazy" in that they do not upgrade their dependencies if the -u flag is used?

[TomWij]

The --exclude suggested by Budoka does that.

[hololeap]

I thought that --exclude only kept specified packages from being installed. I'm asking about changing the behavior of emerge, not a workaround for a specific package. That's ok. I figure if the functionality existed, someone would have mentioned it by now.

I see that Paludis has a --lazy flag, so maybe I'll look into using that. Thanks for the suggestions, though. I didn't know about the firmware flag.

[SiberianSniper]

Whenever I mask off future versions of a package, it seems useful to copy over the package directory from /usr/portage/abc/xyz to /usr/local/portage/abc/xyz and add PORTDIR_OVERLAY="/usr/local/portage" to /etc/make.conf. That way, should you ever need to recompile something, you'll be somewhat protected from your version - or the package as a whole - being removed from the main portage tree.

[NeddySeagoon]

SiberianSniper,

The ebuilds can always be recovered from the portage attic.
The sources may be a problem after a package has been removed from the tree.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.