-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No support for install-required-packages.sh for FreeBSD #8130
Comments
Part of the problem here is that users may not want to use binary packages on FreeBSD. There's also the FreeBSD Ports Tree, and some users even just choose to DIY everything. We can't automatically know which people prefer. |
Don't users have a choice here already? If you want to do things manually; go right ahead. If you want to take advantage of our 1-line installer / kickstart we need this. We can take the approach of just I feel like we should do this :) |
No, not really. This script gets run unconditionally whenever you run the kickstart installer. |
Oh yes I'm aware of that; that's not at issue here. And until we have full proper binary packages everywhere we must still support this method of installation. The thing is; in the recent weeks I've been playing around with various *BSD(s) and some users they don't seem at all too grumpy about using If users want to do things manually on their own; that's fine but don't expect our tools to help too much (because you've chosen to do things by hand :/) |
So... When I get back to this (probably on Sat now) I will add support for FreeBSD using |
At least double check that stuff installed through the ports tree will register as existing on the system so we don't overwrite it if it's there. I think it should be picked up correctly, but I'm not certain. |
Fixed by #9413 |
Bug report summary
As per title. See:
OS / Environment
Netdata version
Component Name
Steps To Reproduce
./packaging/installer/install-required-packages.sh
Expected behavior
We support installing all the right tools automatically on FreeBSD without the user having to go find what needs to be installed in our docs or through trial 'n error.
The text was updated successfully, but these errors were encountered: