4 ms·

i agree that most people don't want to bother with mailing lists and/or IRC these days, though there are a couple of alternative options https://www.perkin.org

by jd3 5y ago

i agree that most people don't want to bother with mailing lists and/or IRC these days, though there are a couple of alternative options https://www.perkin.org.uk/pages/pkgsrc-binary-packages-for-osx.html#get-involved https://www.perkin.org.uk/pages/pkgsrc-binary-packages-for-o... https://github.com/joyent/pkgsrc https://github.com/joyent/pkgsrc https://www.netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd https://www.netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd https://pkgsrc.se/net/py-awscli https://pkgsrc.se/net/py-awscli

mdaniel 5y ago
It appears those links made the same assumption as did @alnja8a in the sibling comment: my concern is not, at this moment, bugs in pkgsrc itself rather my concern is with tracking who is working on fixing (in our example at hand) awscli-v2 Now, maybe if I go trawling through mailing lists or (shudder) IRC I can find out what the status is, but that's beyond my level of energy expenditure for some niche packaging system
- jd3 5y ago
  yeah, i definitely think your point stands the only place i know of where you can (easily) report an issue with a specific package is https://github.com/joyent/pkgsrc/issues https://github.com/joyent/pkgsrc/issues