3 ms·
You bundle or create it yourself.. $ apt-get source bash $ cd bash*/ $ quilt new my_urgent_patch $ patch -p1 < ~/my-urgent-patch.diff $ qui
by _wmd 11y ago
You bundle or create it yourself..
$ apt-get source bash
$ cd bash*/
$ quilt new my_urgent_patch
$ patch -p1 < ~/my-urgent-patch.diff
$ quilt add file1 file2
$ quilt refresh
$ dpkg-buildpackage ...
$ dupload ../*.changes
# trigger apt-get upgrade on target machines
- tptacek 11y agoThat's fine. I don't care what you do with your self-built binaries once you manage to build them yourself. But too many firms have no infrastructure in place to do that. They wait for upstreams to synchronize to fix security flaws that they could fix directly.
- coalescence 11y agoscp and "dpkg -i" are readily available, but it's really not that much work to setup a repository (aptly, reprepro, apt-ftparchive etc.) I know I'd personally chose maintaining the system packages and where possible put extraneous language dependencies in packages too (fpm comes in handy as it can deal with a variety of packages, gem, npm etc). It makes life a lot simpler when it comes to administering a bunch of systems and trying to keep things consistent.