175,187c175,191 < einfo "WARNING: The default behavior for 'emerge rsync' is to have --clean enabled." < einfo "Please back up any modified files in your Portage tree before running emerge" < einfo "rsync." < echo < einfo "You may want to move any custom ebuilds to a new directory, and then set" < einfo "PORTDIR_OVERLAY (in /etc/make.conf) to point to this directory. For example," < einfo "make a /usr/portage.local/sys-apps/foo directory and put your ebuild in there." < einfo "Then set PORTDIR_OVERLAY=\"/usr/portage.local\" Portage should see your" < einfo "personal ebuilds. NOTE: PORTDIR_OVERLAY support is *beta* code; it may not" < einfo "work correctly yet." < echo < echo < } --- > t=`egrep "^PORTDIR_OVERLAY=" /etc/make.conf | sed -e "s/.*='//" -e "s/'$//"` > if [ -n ${t} ]; then > > einfo "WARNING: The default behavior for 'emerge rsync' is to have --clean enabled." > einfo "Please back up any modified files in your Portage tree before running emerge" > einfo "rsync." > echo > einfo "You may want to move any custom ebuilds to a new directory, and then set" > einfo "PORTDIR_OVERLAY (in /etc/make.conf) to point to this directory. For example," > einfo "make a /usr/portage.local/sys-apps/foo directory and put your ebuild in there." > einfo "Then set PORTDIR_OVERLAY=\"/usr/portage.local\" Portage should see your" > einfo "personal ebuilds. NOTE: PORTDIR_OVERLAY support is *beta* code; it may not" > einfo "work correctly yet." > echo > echo > fi > }
Oh yea... thats a patch to portage-2.0.28.ebuild
to be honest i dont see the benefits of this being worth the time to do this ;) i guess if nick disagrees he can re-open it