Summary: | [TRACKER] Metadata cache breakage, caused by redefining ebuild's SLOT through USE="multislot" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey Popov (RETIRED) <pinkbyte> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | jackdachef, jer, rhill |
Priority: | Normal | Keywords: | Tracker |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=174407 https://bugs.gentoo.org/show_bug.cgi?id=434536 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey Popov (RETIRED)
![]() Example of badly behaviour in some tools: bug #434536 I never got a reply to the mail I sent, is masking with an appropriate warning acceptable? (In reply to Ryan Hill from comment #2) > I never got a reply to the mail I sent, is masking with an appropriate > warning acceptable? Masking the whole USE="multislot" ? Yeah, i think it's fine - SLOT variable in all ebuilds has persistent value with disabled USE="multislot". It should only be package.use.masked, otherwise sys-boot/grub will be affected where the flag is used properly (i.e. without changing metadata). + 01 Oct 2014; Sergey Popov <pinkbyte@gentoo.org> package.use.mask: + Mask USE='multislot' in sys-devel/binutils as well, bug #507808 Er, so now we can't have SLOTted toolchain parts? (In reply to Jeroen Roovers from comment #6) > Er, so now we can't have SLOTted toolchain parts? You can unmask USE="multislot" and use it on your own. But until the breakage will be fixed(by, for example, changing metadata concept in portage) it should not be allowed to be enabled for ordinary users. @jer: more specifically, we can have SLOTted toolchain parts. The problem is having the SLOT be redefined by a USE flag, as is the case for USE=multislot. No more bugs open. Closing the tracker. |