| 1 |
On 02-04-2008 20:23:36 +1100, Matt Michalowski wrote: |
| 2 |
>> From the portage i use for bootstrap: /tools/snapshot/prefix-launcher-1pre.20080225/i586-pc-interix3.5/lib/portage/pym/portage/__init__.py:VERSION="2.2.00.8280-prefix" |
| 3 |
>> If i change the ebuild and hardcode the root user, everything works fine. Is my bootstrap portage too old? |
| 4 |
>> |
| 5 |
>> Cheers, Markus |
| 6 |
>> |
| 7 |
> I had the same problem and I *think* re-emerging coreutils fixed it. |
| 8 |
|
| 9 |
I doubt that. |
| 10 |
|
| 11 |
For bug #212818 [1] I had to make sure that the "root user" which is |
| 12 |
different from the normal "portage user" is retained over Portage |
| 13 |
upgrades. By default, "root user" is set to the same value as "portage |
| 14 |
user", hence older Portage ebuilds didn't set this value. |
| 15 |
|
| 16 |
The problem with setting "root user" is that this user is not made |
| 17 |
available in the environment somehow. Hence, I have to retrieve it |
| 18 |
using python from the module where it is stored: (indirectly in) |
| 19 |
portage.const. |
| 20 |
|
| 21 |
My naive approach in the ebuild assumes that the portage modules are in |
| 22 |
the PYTHONPATH, which is the case if a) your python is installed by |
| 23 |
Portage, and b) your libdirs are correctly symlinked on a "multilib" |
| 24 |
install (which I'd like to kill, but that put aside). |
| 25 |
|
| 26 |
We can relax a) by modifying the PYTHONPATH within python itself for |
| 27 |
that portage.const call. Won't be very easy, but I think it can be done |
| 28 |
as there should be enough information in the ebuild available. |
| 29 |
|
| 30 |
|
| 31 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=212818 |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Fabian Groffen |
| 36 |
Gentoo on a different level |
| 37 |
-- |
| 38 |
gentoo-alt@l.g.o mailing list |
Archives