On Fri, 3 Jun 2005, Bob Ippolito wrote: > > 2. When I install a bdist-made package, the files have the owner of > > the user that built the package not the user installing the package, > > even though no root authorization is required.
> bdist_mpkg always finds the deepest installation location to install > to, so changing the permissions of existing directories won't > happen. Even if installer does have that bug, it shouldn't matter. bdist_mpkg-build packages *do* change the permissions on existing directories. See for yourself: ----- artoo% ll -d /Library/Python/2.3/ drwxrwxr-x 8 root admin 272 4 Jun 00:11 /Library/Python/2.3/ artoo% installer -pkg LaunchServices-0.2.mpkg -target / installer: Package name is LaunchServices 0.2 installer: Upgrading volume mounted at /. installer: The upgrade was successful. artoo% ll -d /Library/Python/2.3/ drwxrwxr-x 10 admin admin 340 4 Jun 02:45 /Library/Python/2.3/ ----- If you repair permissions it changes it back to the way it was. It does make a difference because some users think you're incompetent if you ruin permissions with your >> 3. What's the deal with PackageManager? What is a "repository", >> exactly, and what format are the packages in a repository? > PackageManager is completely irrelevant. I know PackageManager is unrelated to bdist_mpkg. I'd still like my question answered so that I can put it up on the Wiki. It's this kind of thing that makes macpython so unapproachable---lots of different ways of doing the same thing, some deprecated, some not. Nick _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
