On 06/06/19 06:00, n952...@web.de wrote:
The handbook is great information, but unfortunately, it uses concepts -
specific gentoo concepts - that many readers doesn't know. They are then often
cross-referenced to other pages, which likewise define things based on expected
internal understanding of the mechanisms, goals, and potential scenarios.
I have "read" the handbook - multiple times. But not really understood what it
was saying - and I have decades of development experience.
Consider slots. I'm sure I've read that slots are used to allow multiple ...
versions? configurations? of the same package to be installed. It was
gradually dawning on me, that it's the developer who specifies the slot. Now,
I can't figure out what use case that benefits, but the ability to have slots
react to realities at a particular installation see to me to make a lot of
sense. So, there must be something basic that I don't understand.
I think cases like my simple case would help new comers and I'm hoping to make
a blog describing it, once I fully understand the implications.
In trying to update portage (before I update my system), I have this:
/!!! All ebuilds that could satisfy
">=dev-python/setuptools-34[python_targets_pypy(-)?,pn_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-pyth-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]"
have been mas//
//!!! One of the following masked packages is required to complete
your request://
//- dev-python/setuptools-9999::gentoo (masked by: EAPI 7)//
//- dev-python/setuptools-41.0.1::gentoo (masked by: EAPI 7)//
//- dev-python/setuptools-41.0.0::gentoo (masked by: EAPI 7)//
//- dev-python/setuptools-40.9.0::gentoo (masked by: EAPI 7)//
//- dev-python/setuptools-40.8.0::gentoo (masked by: EAPI 7)//
//- dev-python/setuptools-40.7.3::gentoo (masked by: EAPI 7)//
//- dev-python/setuptools-40.6.3::gentoo (masked by: backtracking:
slot conflict)//
//- dev-python/setuptools-36.7.2::gentoo (masked by: backtracking:
slot conflict)/
Looking at https://packages.gentoo.org/packages/dev-python/setuptools
shows that the only two versions stable for am64 are 40.6.3 and 36.7.2.
What is *backtracking* and how can I have a *slot conflict *if it's the
developers who determine what version sits in a slot?
One might say, I have a package already dependent on /setuptools/ and
it's not the right one, but how can it be that two different versions
want to go into the same slot?
Backtracking is something to do with dependency checking. I haven't
seen any explanation of what goes on in dependency checking and why
backtracking is necessary. Can someone point to an explanation?
My emerge output goes on to say:
/The current version of portage supports EAPI '6'. You must upgrade
to a//
//newer version of portage before EAPI masked packages can be
installed.//
//(dependency required by "app-portage/gemato-9999::gentoo" [ebuild])//
//(dependency required by
"sys-apps/portage-2.3.66-r1::gentoo[-build,rsync-verify]" [ebuil//
//(dependency required by "portage" [argument])//
//For more information, see the MASKED PACKAGES section in the emerge//
//man page or refer to the Gentoo Handbook.//
/
Is this telling me that I have to *first* update my system and *then*
update portage?
