[gentoo-portage-dev] Re: QA Notice: ECLASS 'foo' inherited illegally

[Duncan]

Brian Harring <ferringb@×××××.com> posted
20060424103851.GD11230@nightcrawler, excerpted below, on  Mon, 24 Apr 2006
03:38:51 -0700:

> When it's (typically) not a valid bug in the ebuild-
> 1) binpkg merging, setup phase.
> 2) (pre|post)(inst|rm)
> 3) config phase.
> 4) When you've gone and screwed with PORTAGE_TMPDIR location, or
> wiped the env file when walking through the phases.
>
> Basically, portage doesn't always reuse the saved env properly- since
> the check relies on a proper env, it gets false positives.
>
> Fixing up the env handling is problematic- basically, that env _needs_
> to be reused (both the relevant portage snippets of it, and eclass).

Old post I know but I'm just getting back to it...

It looks like most of what I see isn't valid, then, as I have
PORTAGE_TMPDIR=/tmp which is your point 4.

Thanks for the bug reference and commentary on env handling.  It's
particularly illuminating in light of the paludis discussion I had
followed on gentoo-dev.



-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-portage-dev@g.o mailing list