1. I had to inject virtual/python-2.3 to emerge rdiff-backup. 2. The executable gets installed into /System/Library/Frameworks/Python.framework/Versions/2.3/bin/, not /usr/bin.
similar problem with rdiff-backup-0.12.7 (stable): binary is installed in: /System/Library/Frameworks/Python.framework/Versions/2.3/bin rdiff-backup & librsync emerged without errors (did not need to inject virtual/python-2.3) after adding ppc-macos keyword.
I keyworded librsync, since that works just fine. I am not a python user, so I am not sure what the desired installation location is for python scripts such as this. I can override the install directories easily, but should we? Other devs: comments on this?
can we come to a final conclusion here? Maybe we can just make it within one year ;) I tried rdiff-backup-0.13.6 and it compiled fine. Personally I don't care if the files are being installed in the frameworks dir. If they work fine, then it's ok with me. If we decide later on this is wrong, then "emerge unmerge" always knows exactly where it's files are.
As far as I can see, I believe the general consensus to be to install to the framework for now. We can always change that in the future if it becomes a problem. *makes a note to put that in the new unspoken general policy guide*
If you have a framework python, packages should be installed to the sitedir. as its the 'Apple Way'. For packages dependencies like scons, you should add this to your profile.bashrc or else portage won't be able to find the tools. Adding the same lines to the bash profile in coreutils-darwin would probably be the user friendly thing to do as well. # add Python.framework dirs to path [ -d /System/Library/Frameworks/Python.framework/Versions/Current/bin ] && \ export PATH="${PATH}:/System/Library/Frameworks/Python.framework/Versions/Current/bin" [ -d /Library/Frameworks/Python.framework/Versions/Current/bin ] && \ export PATH="${PATH}:/Library/Frameworks/Python.framework/Versions/Current/bin"
so, what exactly do you suggest, kito? What has to be done to correctly fix this bug? I like to see this one gone due to its age.
Ok, I added the Python.framework bin directories to profile.bashrc, so portage can use python tools if it needs. Still should probably be added to the users bash.profile, but thats not imperative. I would say if it works, it should be ready for ~ppc-macos, and close it out =)
it appears to work and even see MacOSX specifics: ----------------------------------------------------------------- Detected abilities for source (read only) file system: Access control lists Off Extended attributes Off Mac OS X style resource forks On Mac OS X Finder information On ----------------------------------------------------------------- rdiff-backup-0.13.6 ~ppc-macos in CVS
