Hi,
yeah, that's what I decided to do but sometimes, it mixed between
install/build between both repository.
still, not too annoying.
Make sure you run portindex in your local repository after you've added new
ports, or MacPorts will not find them and use those from the main tree.
--
Hello,
I have several Portfile in the pipe and more questions arising which don't
find solutions in the guide.
- when updating an existing port, is it recommended to copy in your own
depot (own user) or work on the existing one (as root)? in the first case,
it seems that not all action are
At 10:43 AM -0500 2/28/14, Julien T wrote:
- there is a startupitem option but it does not seem any way to
include a cron-like job through launchd? script/exec to launch every
day/month. So I suppose for now, we include our own file.
I won't try to handle all your questions! ;)
launchd
Hi,
- when updating an existing port, is it recommended to copy in your own depot
(own user) or work on the existing one (as root)? in the first case, it
seems that not all action are prioritizing repositories in the same order
(install and before).
I'd recommend copying it so
(1) you can
2014-02-28 11:09 GMT-05:00 Clemens Lang c...@macports.org:
- when updating an existing port, is it recommended to copy in your own
depot
(own user) or work on the existing one (as root)? in the first case, it
seems that not all action are prioritizing repositories in the same order
