This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients alexis, eric.araujo, tarek, vinay.sajip
Date 2011-10-14.20:55:37
SpamBayes Score 1.7155756e-06
Marked as misclassified No
Message-id <1318625738.65.0.542402995914.issue12405@psf.upfronthosting.co.za>
In-reply-to
Content
> If one project creates a/b/thing and another project uses
> a/b/otherthing, then the directories would be recorded in the first
> project’s RECORD, but they should be removed only when both projects
> are removed.

I'm not sure what you mean by "using". AFAIK, each distribution's files (recorded in RECORD) would be unique to that distribution (else distros like Debian will have problems, since files are owned by one package and one package only).

I think all that is needed is as follows:

1. Record any directories that are created in RECORD, ideally bottom-up.

2. On uninstallation, remove all .pyc/.pyo files and __pycache__ directories, and remove all directories named in RECORD, unless they are non-empty (once .pyc/.pyo and __pycache__ are removed).

If you are talking about dependencies between dependencies, I still don't see what your point is. IIUC, if distA depends on distB, distA's RECORD will contain all files which were installed as part of the installation of distA, and likewise for distB.
History
Date User Action Args
2011-10-14 20:55:38vinay.sajipsetrecipients: + vinay.sajip, tarek, eric.araujo, alexis
2011-10-14 20:55:38vinay.sajipsetmessageid: <1318625738.65.0.542402995914.issue12405@psf.upfronthosting.co.za>
2011-10-14 20:55:38vinay.sajiplinkissue12405 messages
2011-10-14 20:55:37vinay.sajipcreate