#42725 closed enhancement (fixed)
Use modern tools for 'port pkg' on newer OS versions
| Reported by: | rob@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | MacPorts 2.4.0 |
| Component: | base | Version: | 2.2.1 |
| Keywords: | Cc: | cooljeanius (Eric Gallager), ci42, plm_macports@…, macports-20081001@…, mroman@…, robertoschwald (Robert Oschwald), mkae (Marko Käning), antonbachin@…, akkornel (A. Karl Kornel), ctreleaven (Craig Treleaven), eduo@… | |
| Port: |
Description
PackageMaker was deprecated a long time ago, and is not a usable app on the latest version of OS X. The latest version available from the developer portal is from a few years ago.
Creating installers should use 'pkgbuild' and 'productbuild' command line tools to create flat packages, which is the current standard.
Change History (20)
comment:1 Changed 11 years ago by cooljeanius (Eric Gallager)
| Cc: | egall@… added |
|---|
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → base |
|---|
comment:4 Changed 11 years ago by plm_macports@…
Replying to rob@…:
PackageMaker was deprecated a long time ago, and is not a usable app on the latest version of OS X. The latest version available from the developer portal is from a few years ago.
Creating installers should use 'pkgbuild' and 'productbuild' command line tools to create flat packages, which is the current standard.
I find a link to add "Auxiliary Tools for Xcode - Late july 2012" from developer.apple.com to the late Xcode installation (https://testingmachine.eu/blog/-/blogs/compiling-opensc-0-13-under-osx-10-9) but it's not a solution for me. It's just a way to temporarly patch MacPorts to wait the "pkgbuild" and "productbuild" integrate MacPorts process. I'm not a developer, so I am just waiting...
comment:9 Changed 9 years ago by RJVB (René Bertin)
Having found and used that PackageMaker version myself yesterday, I'd say that it calls pkgbuild and productbuild.
The easy/evident quickfix (waiting for a release with a more proper fix) would be to check with Apple if MacPorts can redistribute the application, and ship it in a port.
comment:11 Changed 9 years ago by jmroot (Joshua Root)
Contrary to the assertion in the description, PackageMaker still works fine on El Capitan. But yeah, we should use the modern method on systems where it works.
comment:12 Changed 9 years ago by jmroot (Joshua Root)
| Summary: | 'port pkg' still requires PackageMaker.app → Use modern tools for 'port pkg' on newer OS versions |
|---|---|
| Type: | defect → enhancement |
comment:13 Changed 8 years ago by antonbachin@…
Fixing this would be very helpful. I am building packages inside Travis build workers, which don't seem to have PackageMaker installed. They do have pkgbuild and productbuild.
I suppose I can ask Travis developers to install PackageMaker in OS X images, but it seems like the right place to fix this is MacPorts.
I'm not aware of any legitimate way to separately install PackageMaker without logging in as a developer from the build workers, so this is a showstopper for that process.
Travis build environment summary: https://docs.travis-ci.com/user/osx-ci-environment/#OS-X-Version
comment:15 Changed 8 years ago by antonbachin@…
FYI I am building MacPorts with this patch, to use pkgbuild and get around the problem in Travis: https://raw.githubusercontent.com/aantron/binaries/7f181b71afe650b2be193b978713d3f6b9fab487/src/build/macports/ocaml-4.02/pkg.patch
It's not suitable for inclusion straight into MacPorts, as it throws away conditional code and takes other shortcuts.
comment:19 Changed 8 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:20 Changed 8 years ago by jmroot (Joshua Root)
| Milestone: | → MacPorts 2.4.0 |
|---|
Cc Me!