Closed Bug 777465 Opened 13 years ago Closed 13 years ago

changed virtualenv should be repopulated automatically

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: gps, Unassigned)

References

Details

virtualenv population dependencies aren't hooked up right in client.mk. If build/virtualenv/{packages.txt,populate_virtualenv.py} is touched and you |make -f client.mk|, virtualenv is not repopulated. Currently, we would trigger a virtualenv repopulation by re-running configure. So, I suppose the quick fix is to add the build/virtualenv files to the appropriate configure dependencies. I don't think we should be worried about this happening very often - the virtualenv config files will rarely change. When they do, it could have large implications for the tree, so I think re-running configure is proper. Mike Hommey may have some ideas on this.
Turns out the dependencies in client.mk are proper. I was just doing things wrong on my side.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.