Plenty of ebuilds trigger the "..... installed with user portage"
warning in the latest portage. Probably, a more global fix is required,
because a simple grep for "cp -a" in the portage tree returned 411
ebuilds. Chances are most of these would trigger the warning, and that
they are not the only ones. There are also ebuilds that "mv" stuff from
"${WORKDIR}" to "${D}" that would also trigger the warning.
I'd like to throw in a few requests to developers:
- Do not use "cp -a" or similar. Better use cp --recursive --dereference
instead. Which makes me think that a function "ecopy" in eutils would
be useful.
- Do not use "mv" to move stuff from ${WORKDIR}. Sequential "ebuild
install"s should produce the same results, and a "mv" would make them
fail or at least make them not install files that have already been
moved.
--
\/ Georgi Georgiev \/ And miles to go before I sleep. -- Robert \/
/\ [EMAIL PROTECTED] /\ Frost /\
\/ +81(90)6266-1163 \/ \/
pgpN22AOwGKMB.pgp
Description: PGP signature
