3 ms·
I can't (easily) add my own ports tree path to a configuration file... Good point. In most cases the solution is to have your application added to the ports t
by cperciva 19y ago
I can't (easily) add my own ports tree path to a configuration file...
Good point. In most cases the solution is to have your application added to the ports tree (unlike certain ungulate/avian operating systems, FreeBSD doesn't mix up religion and computing, so this isn't only an option for free software), but there are certainly cases where that isn't an option.
Distributing software to FreeBSD users is generally done via a tarball with maybe a shell script
I'd say that a more common method is to distribute a package (which can then be installed via pkg_add).
[The ports tree] asks questions using an ncurses interface, which, as far as I can tell, cannot be disabled.
This needs to be documented better: Add BATCH=YES into your environment, and the ports infrastructure will run without pestering you. Of course, there are a few ports which absolutely need to interact with the user (e.g., to have the user accept an EULA) -- if you set BATCH=YES these ports will print an error message rather than installing.
- SwellJoe 19y ago"I'd say that a more common method is to distribute a package (which can then be installed via pkg_add)." Same problems, though, if I need to distribute a dozen or so packages. No repo-based software distribution means my user either has to download and install them all individually. And, when it comes time to upgrade, they have to do it all over again. So, we've had to write our own package management stuff to deal with the frequent updates we roll out (not just FreeBSD...Solaris also has crap package management). "Add BATCH=YES into your environment, and the ports infrastructure will run without pestering you." Lovely. The squeaky wheel does indeed get the grease. I've gotta air my grievances in public more often.
- cperciva 19y agoSame problems, though, if I need to distribute a dozen or so packages. True. This is something which deserves more thought than it has been given by FreeBSD developers. The squeaky wheel does indeed get the grease. No, the squeaky wheel gets told where the grease has been sitting for several years. :-) More seriously, BATCH=YES and DISABLE_VULNERABILITIES=YES (which is needed to install ports with known security vulnerabilities if you have portaudit installed) are two options which lots of people trip over -- they should probably be better documented.