On Aug 24, 2020, at 5:41 PM, Jeffrey Walton <[email protected]> wrote: >> It's also super-silly to expect that MacPorts is taking "responsibility" for >> all upstream projects. > > How so? > > It is a standard audit item.
please cite what "standard" you believe you are auditing MacPorts under. Please explain what the enforcement mechanism is if MacPorts fails this imaginary audit (ie, do you get something other than a refund of the $0 you paid?). How does this audit compel volunteers to fix an issue for you for free? I'm also curious what imaginary audit wouldn't first point out that python2.7 was sunset on January 1, 2020. > You don't get to claim you are using > software X and any problems are someone else's responsibility. I'm pretty sure I can claim whatever I want ;-) > If you > don't want to be responsible for software X, then you don't use it. Ok, so I guess you are also responsible for MacPorts and all of the software that ports exist for because you use it. >> MacPorts is a community-sourced collection of build recipes. It also hosts >> some mirrors for files referenced in those build recipes and the cached >> results of those build recipes. >> >> It's all done by volunteers and if you paid someone for access to them, you >> should follow-up with whomever you paid. > > The only thing super silly is not taking responsibility for it and > then pushing it onto unsuspecting users. I think you misunderstand what MacPorts is. Please re-read the sentence: "MacPorts is a community-sourced collection of build recipes." -- Daniel J. Luke
