I have macports installed and it's using the default
/opt/local location. There are a few packages not in macports and some I tools I wrote that I put in
~/bin. I found myself needing to use these tools by multiple users on my machine and I don't want to have to copy the same binaries over to each user directory.
/opt is a typical suggestion for third-party software and that's why macports uses
/opt/local. However, it doesn't seem like a good idea to put non-macports packages in
/usr is also commonly suggested but I should probably stay away from that for the same reason macports decided not to use it.
It seems that macports exists entirely in
/opt/local, so I am inclined to create a new directory in
/opt/somename, and mimic the structure to have
Perhaps I'm a bit anal, but I can't come up with a name for this directory that makes sense.
/opt/local would have been appropriate, and I wish macports had used
/opt/macports instead. But I'd rather use as much default config as possible so I don't want to change macport's default directory.
So my question is two parts:
- What would you call your custom-package directory in
- If you disagree with putting the stuff in
/opt/somnameor anything else in my strategy above, then would you suggest a reasonable, fairly isolated alternative.
I'm really interested in how people have tackled this in their own environments, and I'm surprised I haven't been able to find any info on this. Also, I realize one option is to just create my own port, but I would like to specifically address the two questions above.