MacPorts user best practices advice regarding libraries/packages/modules

[Kenneth Wolcott]

Hi;

MacPorts user best practices advice regarding libraries/packages/modules

I'm missing something that must be obvious.

Scenario #1:
When I install a MacPorts port and there aren't any
libraries/packages/modules associated with it and I install one or more of
the associated libraries/packages/modules from a different source, what are
the ramifications when updating/upgrading the MacPort port?

Scenario #2: The above secnario but when there are
libraries/packages/modules associated with the port in question and there
are non-MacPorts libraries/packages/modules (from a different source). Same
question as above.

In general, package management is tricky :-)  What are the best practices
for this?

I didn't see anything resembling this in the faq or manual; possibly I
missed it.

I see that there are package managers out there that might be able to work
with both scenarios (Roswell?)

I've got this problem with Emacs, Perl, Python and R (perhaps more that I'm
not recalling at this point).  I've avoided installing non-MacPorts
packages for Scala, OCaml, (others) because I feel certain that I'm going
to end up in a weird position (usually without warning) when it comes to
updating/upgading MacPorts.

Thanks,
Ken Wolcott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20250614/fc261741/attachment.htm>