5 ms·

A while ago there was a post on HN about pkgsrc[1][2][3], which works on Mac, among other platforms. I haven't tried it, but it may be worth a shot. [1]: <http

A while ago there was a post on HN about pkgsrc[1][2][3], which works on Mac, among other platforms. I haven't tried it, but it may be worth a shot. [1]: <https://rubenerd.com/using-netbsds-pkgsrc-everywhere-i-can/ https://rubenerd.com/using-netbsds-pkgsrc-everywhere-i-can/> [2]: <https://news.ycombinator.com/item?id=27293108 https://news.ycombinator.com/item?id=27293108> [3]: <http://www.pkgsrc.org/ http://www.pkgsrc.org/>

mdaniel 5y ago
I checked and it appears to suffer from the same problem as MacPorts in only making the ancient version of awscli available: http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/net/py-awscli/index.html http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/net/py-awscl... I wasn't able to immediately find any issue tracker for pkgsrc packages, and it seems they're a "mailing list and IRC" type setup, which if true means it definitely isn't for me
- alnja8a 5y ago
  why does the protocol by which bugs and problems get tracked matter, its not like you dont have an email address already... the bug reporting tool is mentioned on the packages page but not the most clear. http://www.pkgsrc.org/#index2h1 http://www.pkgsrc.org/#index2h1
  - mdaniel 5y ago
    I did qualify "for me," indicating that system is not the way that I want to interact with a project The answer to your question is that searching years of email threads is not the same UX as navigating to a dedicated page for managing the lifecycle of a (bug|feature) that tracks when I can expect a new, or working, version of -- in this case awscli-v2 -- to show up, or (if reasonable) that I can indicate to others that I'm willing to take responsibility for doing the work to package it, in order to avoid duplicated effort Plus, again for me, I don't need more email traffic in my life
    - alnja8a 5y ago
      I understand for you, and i understand the UX is different but i dont see how github issues are much better, compared to something like lists.sr.ht or lkml. I find github issues are just as disorganized in a lot of projects with lots of closed due to duplicate and etc. guix has a bug tracker backed on email that has the ux i think you might expect, i find at least, it worked (while i contributed to it) just as well as a non email workflow. Anyway I didnt really consider that this is a personal thing so fair enough to not want to deal with the different problems.
- 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
- DemocracyFTW 5y ago
  mailing list, IRC, and CVS, that is...

mdaniel 5y ago

I checked and it appears to suffer from the same problem as MacPorts in only making the ancient version of awscli available: http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/net/py-awscli/index.html http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/net/py-awscl... I wasn't able to immediately find any issue tracker for pkgsrc packages, and it seems they're a "mailing list and IRC" type setup, which if true means it definitely isn't for me

alnja8a 5y ago
why does the protocol by which bugs and problems get tracked matter, its not like you dont have an email address already... the bug reporting tool is mentioned on the packages page but not the most clear. http://www.pkgsrc.org/#index2h1 http://www.pkgsrc.org/#index2h1
- mdaniel 5y ago
  I did qualify "for me," indicating that system is not the way that I want to interact with a project The answer to your question is that searching years of email threads is not the same UX as navigating to a dedicated page for managing the lifecycle of a (bug|feature) that tracks when I can expect a new, or working, version of -- in this case awscli-v2 -- to show up, or (if reasonable) that I can indicate to others that I'm willing to take responsibility for doing the work to package it, in order to avoid duplicated effort Plus, again for me, I don't need more email traffic in my life
  - alnja8a 5y ago
    I understand for you, and i understand the UX is different but i dont see how github issues are much better, compared to something like lists.sr.ht or lkml. I find github issues are just as disorganized in a lot of projects with lots of closed due to duplicate and etc. guix has a bug tracker backed on email that has the ux i think you might expect, i find at least, it worked (while i contributed to it) just as well as a non email workflow. Anyway I didnt really consider that this is a personal thing so fair enough to not want to deal with the different problems.
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
DemocracyFTW 5y ago
mailing list, IRC, and CVS, that is...