I installed FreeBSD 11.1 on Lenovo T410. I use dwm. I installed sterm package. The message I get after starting: " csh: The terminal database could not be opened csh: using dump terminal settings " Additionally: the fonts here are really, really small.
(In reply to Wojciech A. Koszek from comment #0) Did you follow instructions in pkg-message?
Piotr, I didn't. apt-get never spits out anything, and OpenBSD's 'pkg' never spat out anything during installation either (or at least I didn't notice), and it worked fine. You get very nicely looking fonts by default on X11 in OpenBSD (though: our vt console fonts look better than theirs) But even if I did, installing stuff takes a long time, so I usually do: pkg install package1 package2 package3 And the console log I pretty much never inspect if I see that the overall operating ended up with success. My point is: this stuff should work out-of-the-box without having me to read anything.
(In reply to Wojciech A. Koszek from comment #2) FWIW, it works out of the box on 12.0-CURRENT[1]. Maybe we could poke someone to backport those changes. [1]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226632
(In reply to Wojciech A. Koszek from comment #2) Well, pkg-message is there for a reason. If there were unnecessary, they wouldn't be there. If you refuse to read them, it's not anyone's problem but yours. If you read the pkg-message for this particular port, you would have saved your time, my time and you would get working st 3 days ago. You would have also found out why running those magic commands in pkg-message is necessary and that it will be fixed in future FreeBSD -RELEASE versions (including 11.2).
What you say isn't true. If we both spend 2 hours here, maybe it'll save 30min for each 10 people who try FreeBSD, then it's a win. I'm just giving you my point of view and feedback. You must admit what I said isn't unrealistic usecase. I dug up an old script of mine with FreeBSD 'pkg install'. I sourced it to shell and that's it. I don't observe pkg-messages being spitted out. Anyway, back on technical stuff: === message === * Install tic (included in devel/ncurses) * Run # tic -C -K -s -x %%DATADIR%%/st.info >> /usr/share/misc/termcap # cd /usr/share/misc # cap_mkdb termcap == Why not to make 'tic' a dependency? Why not put these commands in post-install step in port's Makefile?
(In reply to Wojciech A. Koszek from comment #5) Since it touches base system, users should do it on their own. I don't want to modify system files.
All right. We got somewhere here. I guess our ports subsystem doesn't support /usr/local/share/misc/termcap, and from grepping I can see only dwm uses sterm, so spending more time on this makes little sense.
(In reply to Wojciech A. Koszek from comment #7) We may still ask someone to backport those changes from 12 to 11-STABLE so that it is included in 11.2. :)
(In reply to Mateusz Piotrowski from comment #8) 11-STABLE already has this commit.
(In reply to Piotr Kubaj from comment #9) Yes, it was done in base r332044 so I guess there is nothing more to do here.