Changing the Install Volume

19 views
Skip to first unread message

Kris Lou

unread,
Aug 23, 2018, 3:47:42 PM8/23/18
to the-l...@googlegroups.com
I'm trying to deploy a file and run a postinstall script on to a different volume than the Boot Volume (creating packages with The Luggage for Bootstrappr deployment).

I've found "ROOT_ONLY=true" in luggage.make, and tried to override this in my Makefile.  Is this the proper way to do this? 

Actually, does the ROOT_ONLY switch do anything with pkgbuild?

Thanks,

-Kris

--

-->Makefile contents<--

include /usr/local/share/luggage/luggage.make

TITLE=Munki_Postinstall
REVERSE_DOMAIN=biz.axlmusiclink
PACKAGE_VERSION=6.0.0
ROOT_ONLY=false
PAYLOAD=\
pack-preflight \
pack-script-postinstall \

l_usr_local_munki: l_usr_local
@sudo mkdir -p ${WORK_D}/usr/local/munki
@sudo chown -R root:wheel ${WORK_D}/usr/local/munki
@sudo chmod -R 755 ${WORK_D}/usr/local/munki
pack-preflight: l_usr_local_munki
@sudo ${CP} -R preflight ${WORK_D}/usr/local/munki/preflight
@sudo chmod 755 ${WORK_D}/usr/local/munki/preflight
@sudo chown root:wheel ${WORK_D}/usr/local/munki/preflight

-->make pkg output <--

make -e pack-preflight pack-script-postinstall 

******************************************************************


Using /usr/bin/pkgbuild, make sure scripts are

named preinstall/postinstall


Also check your pack-script-* stanzas in PAYLOAD


******************************************************************


Disabling bundle relocation.

If you need to override permissions or ownerships, override modify_packageroot in your Makefile

Creating /tmp/the_luggage/Munki_Postinstall-6.0.0/payload/Munki_Postinstall-6.0.0.pkg with /usr/bin/pkgbuild.

sudo /usr/bin/pkgbuild --root /tmp/the_luggage/Munki_Postinstall-6.0.0/root \

--component-plist /tmp/the_luggage/Munki_Postinstall-6.0.0/luggage.pkg.component.plist \

--identifier biz.axlmusiclink.Munki_Postinstall \

--filter "/CVS$" --filter "/\.svn$" --filter "/\.cvsignore$" --filter "/\.cvspass$" --filter "/(\._)?\.DS_Store$" --filter "/\.git$" --filter "/\.gitignore$" \

--scripts /tmp/the_luggage/Munki_Postinstall-6.0.0/scripts \

--version 6.0.0 \

--ownership preserve --quiet \

/tmp/the_luggage/Munki_Postinstall-6.0.0/payload/Munki_Postinstall-6.0.0.pkg


Mike Solin

unread,
Sep 3, 2018, 9:58:48 PM9/3/18
to the-l...@googlegroups.com
To be honest, I haven’t tried. If you’re not having success with overriding ROOT_ONLY, might I suggest munki-pkg?


I’ve kicked around the idea of moving from The Luggage myself, but it’d be a large task. I haven’t needed to install pkgs on non-boot volumes, so this issue hasn’t come up for me.

--
You received this message because you are subscribed to the Google Groups "The Luggage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to the-luggage...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kris Lou

unread,
Sep 4, 2018, 1:36:46 AM9/4/18
to the-l...@googlegroups.com
I think that ROOT_ONLY is leftover from packagemaker, so no longer effective.  As you can see, the pkgbuild output is basically unchanged.

And standard Luggage/pkgbuild packages are able to installed on non-boot volumes, so no worries there.  In my initial testing, it took a while to figure out that the installation GUI wouldn't prompt to change volumes if it didn't detect a 2nd volume present ...

-Kris
To unsubscribe from this group and stop receiving emails from it, send an email to the-luggage+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "The Luggage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to the-luggage+unsubscribe@googlegroups.com.

Mike Solin

unread,
Sep 4, 2018, 8:15:28 AM9/4/18
to the-l...@googlegroups.com
Cool, thanks! Good to know. The Luggage lives on for another day. :)
To unsubscribe from this group and stop receiving emails from it, send an email to the-luggage...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages