5 ms·
Why wouldn't you build a newer package for 13.04, or try using the trusty package on it? I can't imagine waiting for a new OS release every time I needed a newe
by bretthoerner 13y ago
Why wouldn't you build a newer package for 13.04, or try using the trusty package on it? I can't imagine waiting for a new OS release every time I needed a newer package.
- kawsper 13y agoIt is not really often I need a newer package than what is available, I can only think of Beanstalk because if this issue. I am not really that used to build my own packages, but it is something I want to learn. And I didn't know that I could download from another version, I will look into it, thanks ! :)
- nisa 13y agoapt-get build-dep beanstalkd apt-get source beanstalkd # or in your case, download the newer source-package cd ./beanstalkd-1.x.x dpkg-buildpackage -rfakeroot -us -uc This should do the trick. There are a lot of variations regarding the last line. Just google for Debian packaging or Ubuntu packaging tutorials. It really works well for minor changes. If you need to deploy it to several machines it's also possible to add a custom flag to the package version...
- wiredfool 13y agoAnd it's an unbelievable pain in the ass when they change packaging styles, and the new src packages aren't compatible with the older build tools. IIRC, that happened between 10.04 and 12.04.
- danudey 13y agoIt did, but it's only relevant for packages which actually updated their build scripts. A huge proportion of packages from 12.04 will still build fine on 10.04 (which I've been doing in order to backport certain packages to install).