Post AxIwO1QSa3kK7H6fce by encthenet@flyovercountry.social
 (DIR) More posts by encthenet@flyovercountry.social
 (DIR) Post #AxIr3fp4gtODYN67NI by encthenet@flyovercountry.social
       2025-08-18T18:13:25Z
       
       0 likes, 0 repeats
       
       Omg, pkg removed git because the latest set of packages doesn't have git which of course makes things more difficult now that portsnap has been removed.I didn't read closely what was being removed because I didn't think that FreeBSD would deploy a set of packages that doesn't have such a fundamental package.Just learning again that arm64 packages are a shit show.#FreeBSD
       
 (DIR) Post #AxIr3hcO12Qd7bB0sK by encthenet@flyovercountry.social
       2025-08-18T18:42:22Z
       
       0 likes, 0 repeats
       
       Wtf happened to the FreeBSD ports tree?  I can't just make install -j8 a port anymore.  It just breaks or throws up dialogs asking to be configured.  Even setting BATCH doesn't make those dialog prompts go away.If -j 8 breaks the ports tree so badly, why doesn't the mk infrastructure error out when present?  And forcing a single threaded build is just painful.
       
 (DIR) Post #AxIr3irJP1xgyBARmK by picofarad@noauthority.social
       2025-08-18T18:56:02Z
       
       0 likes, 0 repeats
       
       @encthenet this sounds quite broken. Maybe they lost a good maintainer?
       
 (DIR) Post #AxIwO1QSa3kK7H6fce by encthenet@flyovercountry.social
       2025-08-18T19:55:44Z
       
       0 likes, 0 repeats
       
       @picofaradLooks like it just needs to be documented.(And imo fixed so a bare dot works.)https://freeradical.zone/@ax6761/115051307279973939