Re: Can some ports install config files inside '/usr/local/etc'?
On Dec 11, 2021, at 23:54, fgyamauti2 fgyamauti2 wrote: > The weird thing is that everything suspicious inside '/usr/local/etc' is a > configuration file of stuff that is related to MacPorts. More precisely, I > have suspicious folders named 'fonts' (from fontsconfig), 'gnutls', > 'openldap', 'openssl@1.1', 'pkcs11'. Now, when I search the name of each > folder, there's always another folder with similar or equal name further > inside '/opt/local/' (so something like 'opt/local/a/b/c/d/gnutls') MacPorts keeps the Portfiles of all (tens of thousands of) existing ports on your system in /opt/local/var/macports/sources. This collection is called the "ports tree". When you ask MacPorts to install something, it does so by following the recipe in the corresponding Portfile. Those Portfiles are what get updated when you run "sudo port sync" or "sudo port selfupdate". So it's not surprising at all that when you search your drive for a common software program name, you find a directory with that name within MacPorts. MacPorts hasn't ever installed any directory called "openssl@1.1" as far as I know, but Homebrew does. MacPorts does use the convention "portname @version_revision+variants" when referring to ports, but that notation does not appear in directory names.
Re: Can some ports install config files inside '/usr/local/etc'?
Thanks for the replies Nothing in macports will be installing to /usr/local. If you have anything > in that area it has been put there by some other means. Maybe homebrew?, > but also a number of third party installers sometimes use this directory as > well (which are the reasons why MacPorts specifically ignores this area). > As mentioned also by Chris in the above reply and Ralph in the previous one, I've had Homebrew installed only for a short amount of time. Still, however, unless I'm getting too old, I don't recall installing unbound through Homebrew (I used Homebrew for 2 days and uninstalled it in fear of screwing up something in TeXLive). So unless it's installed by default... Well, also I should mention that I've set unbound-control. The weird thing is that everything suspicious inside '/usr/local/etc' is a configuration file of stuff that is related to MacPorts. More precisely, I have suspicious folders named 'fonts' (from fontsconfig), 'gnutls', 'openldap', 'openssl@1.1', 'pkcs11'. Now, when I search the name of each folder, there's always another folder with similar or equal name further inside '/opt/local/' (so something like 'opt/local/a/b/c/d/gnutls') and a folder related to macports is always on the path (for instance, 'macports' and 'rsync.macports.org'). Also, inside '/opt/local/lib' I have stuff from Python 3.9 and Python 3.10. But I've only installed these through MacPorts. That's weird. Well, I've installed pip through Python 3.10 and ensurepip. That still doesn't explain it, I suppose...
Re: Can some ports install config files inside '/usr/local/etc'?
On Sat, 11 Dec 2021, Chris Jones wrote: > Nothing in macports will be installing to /usr/local. If you have > anything in that area it has been put there by some other means. Maybe > homebrew?, but also a number of third party installers sometimes use > this directory as well (which are the reasons why MacPorts specifically > ignores this area). The "/usr/local" tree is quite a common destination on other systems such as FreeBSD; I use it on the Mac to separate my own stuff from MacPorts' stuff as well. -- Dave
Re: Can some ports install config files inside '/usr/local/etc'?
Nothing in macports will be installing to /usr/local. If you have anything in that area it has been put there by some other means. Maybe homebrew?, but also a number of third party installers sometimes use this directory as well (which are the reasons why MacPorts specifically ignores this area). > On 11 Dec 2021, at 5:11 am, fgyamauti2 fgyamauti2 > wrote: > > > Hi, > > Apparently some ports that I've installed are making directories inside > '/usr/local/etc' with example configuration files. Still the installed ports > themselves seem to only listen to stuff inside '/opt/local/etc'. > > For instance, I have an 'unbound' folder inside both. In the former, it > contains 'unbound.config', while in the latter it contains 'root.key' and > 'unsound.config-dist' (a file with contents identical to 'unbound.config'). > That seems to happen to particular ports only, though. Anyone experiencing > that? Are these folders really unnecessary? > > Thanks in advance, > FY >
Re: Can some ports install config files inside '/usr/local/etc'?
* fgyamauti: > Apparently some ports that I've installed are making directories > inside '/usr/local/etc' with example configuration files. That seems unlikely. Have you perhaps installed both MacPorts and Homebrew on your Mac? AFAIK, Homebrew uses /usr/local/* to store its installation files. -Ralph
Re: Can some ports install config files inside '/usr/local/etc'?
On Dec 11, 2021, at 12:11 AM, fgyamauti2 fgyamauti2 wrote: > Apparently some ports that I've installed are making directories inside > '/usr/local/etc' with example configuration files. Still the installed ports > themselves seem to only listen to stuff inside '/opt/local/etc'. They shouldn't be. > For instance, I have an 'unbound' folder inside both. In the former, it > contains 'unbound.config', while in the latter it contains 'root.key' and > 'unsound.config-dist' (a file with contents identical to 'unbound.config'). > That seems to happen to particular ports only, though. Anyone experiencing > that? Are these folders really unnecessary? On my system(s) the unbound port does not create anything in /usr/local/etc `port contents unbound` doesn't show any unusual files and I don't see any part of the portfile that would be doing that on your system. -- Daniel J. Luke
