GSoC Project: Revitalizing Pallet

Joshua Root jmr at
Wed May 6 22:18:05 PDT 2015

You'd have to ask rhwood for a definitive answer, but I assume because
that's what shipping containers at a port are full of? :)

- Josh

On 2015-5-7 13:35 , David Strubbe wrote:
> Why is it called Pallet?
> David
> On Wed, May 6, 2015 at 8:59 PM, Mark Anderson <emer at
> <mailto:emer at>> wrote:
>     I love it. I agree with Ryan, I think a portfile Editor/IDE should
>     be a separate MacPorts.framework project from Pallet.
>     —Mark
>     _______________________
>     Mark E. Anderson <emer at <mailto:emer at>>
>     On Wed, May 6, 2015 at 8:40 PM, Ryan Schmidt
>     <ryandesign at <mailto:ryandesign at>> wrote:
>         On May 6, 2015, at 5:14 PM, Kyle Sammons wrote:
>         > My name's Kyle Sammons and I've been accepted into this years
>         GSoC. I was also a GSoC participant for MacPorts last year
>         working on Project "Clean-up Stuff", which created the "port
>         doctor" and "port reclaim" commands.
>         >
>         > My project for this year is to get Pallet, the MacPorts GUI,
>         up and running with the support for newest versions of OS X and
>         XCode. After that, I intend to give it, and the Framework, some
>         more modern-day-MacPorts features. No features are set in stone
>         as of yet, but I'm considering adding doctor, reclaim,
>         rev-upgrade, a progress bar, or possibly even the ability to
>         edit portfiles.
>         >
>         > Once again, none of these potential features are set in stone
>         so if you guys would like to suggest any that would be nice to
>         have, or have some questions/concerns about the project, feel
>         free to shoot me an email.
>         Great idea! I would only propose that you *not* pursue the idea
>         of letting people edit portfiles, as that opens up lots of
>         possibilities for problems. Pallet should be the utility for
>         users who are not comfortable using the command line. Those
>         users don't need to be editing portfiles.

More information about the macports-dev mailing list