[issue31049] macOS Python package receipts do not have version numbers

[Shea Craig]

New submission from Shea Craig:

The Python installer package for macOS is versioned, however, the included sub 
packages have no version information. This results in the receipts having no 
version. Many enterprise software management tools rely on the receipt 
information to determine whether something is present and whether it's due for 
an update. We use Munki, are are currently working around this issue, but 
ideally the subpackages would have the version info included.

$ for PKG in $(pkgutil --pkgs | grep org.python);do pkgutil --pkg-info $PKG;done
package-id: org.python.Python.PythonApplications-3.6
version: 0
volume: /
location: Applications
install-time: 1494351483
package-id: org.python.Python.PythonDocumentation-3.6
version: 0
volume: /
location: 
Library/Frameworks/Python.framework/Versions/3.6/Resources/English.lproj/Documentation
install-time: 1494351483
package-id: org.python.Python.PythonFramework-3.6
version: 0
volume: /
location: Library/Frameworks/Python.framework
install-time: 1494351483
package-id: org.python.Python.PythonUnixTools-3.6
version: 0
volume: /
location: usr/local/bin
install-time: 1494351483

--
components: macOS
messages: 299257
nosy: Shea Craig, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: macOS Python package receipts do not have version numbers
versions: Python 3.6

___
Python tracker 
<http://bugs.python.org/issue31049>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24502] OS X installer provides flat sub-packages with no version numbers

[Shea Craig]

Shea Craig added the comment:

For what it's worth, I manage a lot of Macs and know a lot of people in similar 
roles at major enterprises. We greatly prefer installer packages for automated 
installation, and end up having to repackage installer apps routinely for 
products that don't use that mechanism. If it's not an app that can be dropped 
into the Applications folder, Apple installer packages really are the best 
format for enterprise deployment.

>From the development side I'm not familiar enough with the advantages of 
>trying to use a metapackage to bundle the contained packages, but I can say 
>that the version numbers all being 0 causes me to have to do some extra work 
>to ensure upgrades can be compared against what's already installed.

I assume the metapackage is used to create the ability for the user to choose 
to exclude some of the subpackages. This is not a feature I use in deploying 
the software, although I recognize its utility.

--
nosy: +Shea Craig

___
Python tracker 
<http://bugs.python.org/issue24502>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com