Re: Package Maker ownership issues
Re: Package Maker ownership issues
- Subject: Re: Package Maker ownership issues
- From: Jakub Bednar <email@hidden>
- Date: Thu, 8 Oct 2009 12:05:50 +0200
On Oct 6, 2009, at 11:25 PM, Iceberg-Dev wrote:
On Oct 6, 2009, at 12:24 PM, Jakub Bednar wrote:
On Oct 5, 2009, at 9:56 PM, Iceberg-Dev wrote:
On Oct 5, 2009, at 11:04 AM, Jakub Bednar wrote:
On Oct 2, 2009, at 5:14 PM, Greg Neagle wrote:
user/group info for filesystem items is _always_ stored as numeric
values.
When you create your user, specify the UID at that time as well.
[...]
Well ok,
You are probably right in 99% of the cases. But I'm installing a
transparent proxy that needs a unique UID in the system to take
advantage of UID matching in firewall rules. Never mind, there are
workarounds. I was just wondering why it is not supported.
Thanks a lot,
Jakub
P.S. There is a bunch of Linux/FreeBSD software that is creating
new user accounts in the system for their purposes. It is just a
normal way of doing things on Linux/FreeBSD. There is also no
problem to create an invisible user without home directory and
password with the dscl utility, so why not support it in Installers?
It is supported since you can do it in a package with a script.
It's just that it would not be a good idea for the Installer to
create a new user account just because there is a file in the package
payload whose owner does not exist on the target system.
Apparently we do not understand each other. I know I can create the
user in a preinstall script and I don't want installer to create him
for me.
What I want is to allow package maker, to store file ownership also by
user name. With this the receipt files after installation will hold
correct user/group specification of the newly created user by my
preinstall script. pkgutil --repair will than work correctly repairing
rights to the user my script has created on the system (and not to the
UID/GID of that user on the system where the installation package was
created, as it is now)
If the package has the user specified by his name and the installer
doesn't find the specified user in the target system when unpacking
the files (after preinstall script), it should return an error and not
unpack the files.
The way I need to go now to make pkgutil --repair work correctly is:
1. Create the user in preinstall script and install the files
2. Execute pkgutill --export-plist to get the current receipt plist
with wrong UID/GID specifications
3. Do some seding to fix the UID/GID to match those of my newly
created user in step 1
4. Execute pkgutil --import-plist to store this fixed plist back in
receipts
This is not really simple way how to have correct receipts stored in
the system.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden