/usr/local/bin/packagemaker: command not found

[tob...@globalmacit.com]

Hi all,

I was having some challenges today with getting back into using The Luggage. I decided to start from the beginning so I downloaded the zip, unpacked it, cd into the directory and ran `sudo make pkg`. I received "/usr/local/bin/packagemaker: command not found".

I just updated Xcode to 6.1 and installed the command line tools. I know packagemaker has been a moving target in the last couple years and i understand that pkgbuild is the new preferred tool. If that is so, why is The Luggage still looking for it?

Anyways, what am I doing wrong and how do I right my ways?

Thank you,

- Tobias

[Nathan Felton]

A number of stanzas have been added/updated to the luggage.make file that will build a pkg using pkgbuild instead of packagemaker, you simply have to include "USE_PKGBUILD=1" at the beginning of your Makefile for it to use it. 

As we have now had a number of Xcode releases since packagemaker has replaced pkgbuild and productbuild, we could really use an overhaul of Luggage. I'm thinking Luggage v2.0 should be built only use pkgbuild and productbuild, but I personally haven't had time to work on such an overhaul.

--
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.

--

Nathan Felton

@n8felton

[tob...@globalmacit.com]

Hi Nate,

Thank you for the quick response. I had tried that trick and had the same error. I tried moving "USE_PKGBUILD=1" to line 3 and got what I expected, which was no change. I even added that to the Makefile in The Luggage download but that still returns the same error.

- Tobias

[Vaughn Miller]

It is not documented very well, but the :

USE_PKGBUILD=1

must come before the 

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

Vaughn Miller

Desktop Engineer

Lafayette College

[tob...@globalmacit.com]

And just like that my morning of frustration comes to an end. Thank you both of you!

[Joe Block]

It's probably well past time we set USE_PKGBUILD=1 by default.

In retrospect, I really wish I'd written Luggage with rake instead of make. Frankly, make's syntax can be a bit convoluted, and the space/tab indentation issue is annoying for new users. Nathan, if you end up starting work on a Luggage 2.0, I really recommend using rake instead.

I'm not administering OS X any more, or I'd seriously consider another rewrite. Third time's the charm, right?

jpb

Don't say the sky's the limit when there are footprints on the moon.

[Nathan Felton]

I'll take a look at it. I have zero experience with rake or ruby, but then again the only thing I know about make is what I've learned from playing with Luggage.

[Allister Banks]

There is cart…
https://github.com/glarizza/Cart/blob/master/Readme.markdown

Allister

[Clay Caviness]

After fighting with git a while, I've made the change to default to pkgbuild (https://github.com/unixorn/luggage/pull/52)

I also merged a few of the other pending pull requests (OpenDirectory configuration https://github.com/unixorn/luggage/pull/35 and disable relocation https://github.com/unixorn/luggage/pull/48).

Clay Caviness
c...@google.com

Macintosh Operations Tech Lead
Google Inc.

[Clay Caviness]

And by fat-fingering a git push and going upstream instead of origin, we now have a pack-var-db-ConfigurationProfiles-Setup-% rule.