Summary: | Using ebuild ... install forces a new configure and make run | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Svein Erik Brostigen <svein.brostigen> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Svein Erik Brostigen
2003-11-21 12:42:17 UTC
Same thing happens with krusader. The ebuiold fails on some docbook issues. Not a proble, I just edited the Makefile and removed 'doc' from the SUBDIR line and built it without errors. When doing ebuild ... install, it rerun configure and amke and resulting in a failuer. Not sure how to get around this one except for fixing the docbook issue. FEATURES=noauto Yes, that works. But, why are some ebuilds re-running the config script when it has already been run? |