Summary: | Portage-2.1* removes /distdir | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Väth <martin> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | critical | Keywords: | REGRESSION |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 115839 | ||
Attachments: | existing clean phase ported from bash to python |
Description
Martin Väth
2006-02-26 14:02:57 UTC
This seems to be caused by `rm -rf "${PORTAGE_BUILDDIR}/distdir"` inside ebuild.sh. Needs a sanity check... I've added a sanity check in dyn_clean() to make sure that PORTAGE_BUILDDIR is not zero length (svn r2800). It seems that PORTAGE_BUILDDIR was unset because portage-2.0.54 (which doesn't set PORTAGE_BUILDDIR) was using the newly installed ebuild.sh from portage-2.1_pre5. Thanks. This sounds reasonable and also decreases the danger that something else is going to havoc if something is fooling around with the environment. Created attachment 80877 [details, diff]
existing clean phase ported from bash to python
IOM ebuild.sh really should only handle ebuild execution rather than random shell tasks. There's no need for the clean phase to be inside ebuild.sh.
I have released the sanity check in 2.1_pre5-r2. |