Summary: | SELinux Handbook: recent systems do not have python2 installed at all | ||
---|---|---|---|
Product: | Documentation | Reporter: | Paweł Hajdan, Jr. (RETIRED) <phajdan.jr> |
Component: | Project-specific documentation | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | selinux |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml?part=2&chap=1 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paweł Hajdan, Jr. (RETIRED)
2012-04-06 08:22:46 UTC
Doesn't it pull this in automatically? We package.use.force USE="python2" for portage in our profiles. That said, we might want to verify if python3 now works fully on SELinux or not. Recent userland utilities already have some Python-3 changes in them (currently marked as ~arch, ETA stabilization 20120430). (In reply to comment #1) > Doesn't it pull this in automatically? I don't know - the stage3 didn't contain python2, and the SELinux Handbook has the following order of operations: 1. eselect python set ... 2. eselect profile set ... 3. emerge -uDNa world Only step #3 has the potential to pull in python2, and I've just done it manually before #1. > We package.use.force USE="python2" for portage in our profiles. Now emerge --depclean --verbose --pretend python:2.7 shows that it's pulled by portage, among others. Fixed in CVS |