Changes between Initial Version and Version 1 of Ticket #64504


Ignore:
Timestamp:
Jan 24, 2022, 1:54:24 AM (2 years ago)
Author:
TruePath (Peter Gerdes)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #64504 – Description

    initial v1  
    11If this issue has been discussed before I apologize.  I looked but I couldn't find it.
    22
    3 About one in four times I run port install (and often just port update) I find that some port has set some kind of docs to be included by default with a build dependency on texlive.  This is super irritating because I need to have texlive installed outside of macports  and I come back after install/update all the time to find I need to remove macports texlive again by hand.  Even examining the ports I'm installing doesn't help because often the offending package is buried deep in the dependency tree (and takes quite awhile to track down)
     3About one in four times I run port install (and sometimes just port update) I find that some port has set some kind of docs to be included by default with a build dependency on texlive.  This is super irritating because I need to have texlive installed outside of macports  and I come back after install/update all the time to find I need to remove macports texlive again by hand.  Even examining the ports I'm installing doesn't help because often the offending package is buried deep in the dependency tree (and takes quite awhile to track down)
    44
    55This could be fixed by allowing users to mark a package as installed and frozen as with apt (or just blocked) but I suspect you've already decided against that.  However, texlive specifically is a huge install that seems to get randomly installed from other packages all the time so maybe something could simply be done on a policy level to  stop packages that don't really need texlive from defaulting to requesting it to build docs.