4 ms·
Yes, but that implicit (I hope) with security upgrades. I do the compiles myself. It is pretty easy to build a set for distribution after compiling once.
by protomyth 11y ago
Yes, but that implicit (I hope) with security upgrades. I do the compiles myself. It is pretty easy to build a set for distribution after compiling once.
- ams6110 11y agoDo you have (or know of) a good set of practices to follow on this? I've tried this in the past but some ports (typically big ones like web browsers) will run out of some resource or other during the build. Also it seems that if you build from ports all the dependencies are built from ports too, even if they're already installed as packages? It ends up taking hours in some cases.
- stsp 11y agoAssuming you're tracking -current sources, it's usually possible to just run the published binary packages from mirrors on top of your own base builds. If library bumps happened, the packages might take a while to catch up, though. What I do is I build a release with patches I'm interested in (my own or other people's). After upgrading my machines to that release I try `pkg_add -u`. If that complains about libraries, I just wait a day or two for a new set of packages to come out and try again. Sometimes I cheat and compile the missing library in a slightly backdated src checkout, or fetch it from a system that happens to have a copy of the right .so file. If all that is too complicated, or if you want -stable instead of -current, try mtier.