I use the following launchd task [1] and shell script [2] to automate weekly updates.
You can remove the reference to "portsign.sh", unless you want to share your compiled ports with another MacPorts installation [3]. [1]: https://gist.github.com/fracai/2324512 [2]: https://gist.github.com/fracai/2324493 [3]: https://trac.macports.org/wiki/howto/ShareArchives2 On Sat, Apr 27, 2013 at 5:55 PM, Clemens Lang <c...@macports.org> wrote: > On Sat, Apr 27, 2013 at 04:16:50PM -0500, Ryan Schmidt wrote: >> And running MacPorts via root instead of via sudo will currently cause some >> problems: >> >> http://trac.macports.org/ticket/34221 > > You could use the workaround I proposed in > https://lists.macosforge.org/pipermail/macports-dev/2013-April/022725.html > (the mail is a reply to a mail that seems to have been moderated from > the list, which is the reasons why it seems to be lacking some context) > > -- > Clemens Lang > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users