From e800887ba35894c848ceb9e94177e24d9e6048ff Mon Sep 17 00:00:00 2001 From: Felix Fietkau Date: Fri, 28 Dec 2007 17:04:38 +0000 Subject: document the feeds system git-svn-id: svn://svn.openwrt.org/openwrt/trunk@10001 3c298f89-4303-0410-b956-a3cf2f4a3e73 --- docs/build.tex | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/build.tex b/docs/build.tex index ef58b0ba7e..54d31c582b 100644 --- a/docs/build.tex +++ b/docs/build.tex @@ -80,10 +80,10 @@ add a new version of one of the components above. \texttt{package} is for exactly that -- packages. In an OpenWrt firmware, almost everything is an \texttt{.ipk}, a software package which can be added to the firmware to provide new features or removed to save space. Note that packages are also maintained outside of the main -trunk and can be obtained from subversion at the following location: +trunk and can be obtained from subversion using the package feeds system: \begin{Verbatim} -$ svn checkout https://svn.openwrt.org/openwrt/packages packages +$ ./scripts/feeds update \end{Verbatim} Those packages can be used to extend the functionality of the build system and need to be @@ -91,15 +91,17 @@ symlinked into the main trunk. Once you do that, the packages will show up in th configuration. From kamikaze you would do something like this: \begin{Verbatim} -$ ls -kamikaze packages -$ ln -s packages/net/nmap kamikaze/package/nmap +$ ./scripts/feeds search nmap +Search results in feed 'packages': +nmap Network exploration and/or security auditing utility + +$ ./scripts/feeds install nmap \end{Verbatim} To include all packages, issue the following command: \begin{Verbatim} -$ ln -s packages/*/* kamikaze/package/ +$ make package/symlinks \end{Verbatim} \texttt{target} refers to the embedded platform, this contains items which are specific to -- cgit v1.2.3