{"id":561,"date":"2015-04-21T03:20:53","date_gmt":"2015-04-21T01:20:53","guid":{"rendered":"http:\/\/hobbykeller.spdns.de\/?p=561"},"modified":"2015-04-22T15:35:19","modified_gmt":"2015-04-22T13:35:19","slug":"adding-custom-packages-to-an-openwrt-image","status":"publish","type":"post","link":"https:\/\/hobbykeller.spdns.de\/?p=561","title":{"rendered":"Adding custom packages to an OpenWRT image"},"content":{"rendered":"

As I use the stable Barrier Braker 14.07 release of OpenWRT, I sometimes run into the problem that the packages included in these releases are either outdated versions or that a package was not yet available in the 14.07 release but is now included in the trunk of\u00a0github package repository<\/a>. In both cases, we either need to replace the outdated version of the package sources with a newer one or add a completely new package to the respective feed of our Barrier Breaker sources.<\/p>\n

The following tutorial shows how this can be accomplished. We will take ddns-scripts as an example of an outdated package to be replaced by a newer version in our image and davfs2 as an example of a package which has to be added as a completely new package to our image sources (davfs2 was not available in the 14.07 feed of OpenWRT but it can be retrieved from the github master trunk).<\/p>\n

Updating the sources<\/h1>\n

When retrieving or refreshing the local source code from which the router image is built, a regular step is to issue a .\/scripts\/feeds\/update -a<\/code> followed by a .\/scripts\/feeds\/install -a<\/code> command in order to update the package sources. The install<\/code> command basically puts a couple of symlinks from the package<\/code> directory into the feeds<\/code> subdirectories.<\/p>\n

So after issuing .\/scripts\/feeds\/update -a<\/code> we are first going to modify the package sources before creating the symlinks by issuing the install -a<\/code> command:<\/p>\n

Download the whole github package repo and extract it to your harddisk.<\/p>\n