Opened at 2013-06-11T15:00:14Z
Closed at 2016-03-26T22:55:21Z
#2001 closed task (fixed)
build binary eggs for macosx-10.9-intel (mavericks)
| Reported by: | tilllt | Owned by: | tilllt |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.11.0 |
| Component: | packaging | Version: | 1.10.0 |
| Keywords: | mac osx 10.9 mountain-lion eggs | Cc: | |
| Launchpad Bug: |
Description
To build binary eggs for OSX you have to install clang through Macports but to install Macports you need XCode-Cli and to install XCode-Cli you need to create a Apple-ID to download it... so i guess it make sense to have the binary eggs for this platform as well.
Attachments (6)
Change History (14)
Changed at 2013-06-11T15:00:49Z by tilllt
Changed at 2013-06-11T15:01:02Z by tilllt
Changed at 2013-06-11T15:02:16Z by tilllt
Changed at 2013-06-11T15:02:52Z by tilllt
Changed at 2013-06-11T15:03:14Z by tilllt
Changed at 2013-06-11T15:06:06Z by tilllt
comment:1 Changed at 2013-06-16T16:41:33Z by daira
- Component changed from unknown to packaging
- Keywords mac mountain-lion added; mountain lion removed
- Milestone changed from undecided to soon
comment:2 Changed at 2013-06-16T16:43:05Z by daira
- Keywords eggs added
comment:3 Changed at 2013-07-12T21:55:27Z by zooko
- Owner changed from daira to tilllt
comment:4 Changed at 2013-07-13T11:45:27Z by tilllt
Is there some sort of template for the provenance files? I don't quite understand what they are used for, if they would contain info about the compiler version etc.pp. i would understand that but just "built by tilllt on his mac" (like it is in some of the ones in the directory) doesn't make a lot of sense nor does it provide info for debugging? or is a pro-forma required file for egg distribution?
comment:5 Changed at 2013-07-13T19:45:44Z by zooko
tillt: the purpose of them is to help people figure out later where the files came from. Like, suppose there's a bug in one of the packages. Or suppose there is a backdoor! The bug (or the backdoor) might be caused the by the specific compiler that you used, for example. We'd like to have a record of who you are, when the package was created, what machine and operating system and compiler was used. I guess that's about it. The ability to contact you (like an email address) would be good. Make sense?
comment:6 Changed at 2013-07-16T17:42:45Z by zooko
And the sha256sum of the .egg file to identify it.
comment:7 Changed at 2014-09-25T16:22:09Z by zooko
- Keywords 10.9 added; 10.8 removed
- Summary changed from build binary eggs for macosx-10.8-intel (osx mountain lion) to build binary eggs for macosx-10.9-intel (mavericks)
comment:8 Changed at 2016-03-26T22:55:21Z by warner
- Milestone changed from soon to 1.11.0
- Resolution set to fixed
- Status changed from new to closed
I've built and published binary wheels for OS-X builds at https://tahoe-lafs.org/deps/ , and have updated the OS-X build instructions (docs/OS-X.rst) to explain the pip --find-links=URL install argument to use them.
These are 10.10 or 10.11 wheels, but I think that's ok these days.. 10.9 is no longer supported by Apple, as far as I know.
Closing this one out.
Dear tillt: Thanks for your work on this!
Could you please provide ".provenance.txt" files, like the ones listed here, so that we can remember where we got these eggs?
Thanks!
https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/