86523 – portage should not run depscan.sh

Bug 86523 - portage should not run depscan.sh

Summary: portage should not run depscan.sh

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:

Reported:	2005-03-24 06:50 UTC by SpanKY
Modified:	2005-07-14 06:58 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SpanKY gentoo-dev

2005-03-24 06:50:13 UTC

not quite sure why depscan.sh was ever added to portage, but there's no reason to run it ...

depscan.sh regenerates init.d cache information and nothing else ... the init scripts themselves are hardy enough to determine whether the cache needs to be updated, so having portage run it after every frickin step is useless

Comment 1 Jason Stubbs (RETIRED) gentoo-dev

2005-07-14 05:47:30 UTC

Fixed on or before 2.0.51.22-r1

Comment 2 Jason Stubbs (RETIRED) gentoo-dev

2005-07-14 06:58:20 UTC

Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.