Re: Busybox Alternatives
- Brick wall, this is head - head, meet brick wall.
Individually, everything makes sense but I have no grasp of the
whole - I think I'm suffering from a general ignorance at this point
so I'll try attacking from the other direction. I'm going to see if
I can do a local build of busy-box w/no changes simply by following
Then I'll come back and bug you some more.
Thanks - and hope to type at you again soon!
--- In firstname.lastname@example.org, "Brian Zhou" <b88zhou@...> wrote:
> The busybox source tarball is actually downloaded from busybox.net.
> This is done on the line with $(WGET) in make/busybox.mk.
> The optware's job is basically unpack, patch if necessary, build
> the appropriate toolchain to target binary(binaries). The last
> to package the distribution into ipk with meta data (description,
> dependencies, etc), together with postinst and prerm script if
> As the name suggests, postinst script is run by ipkg right after
> the files of the package have been installed, usually during "ipkg
> install". And prerm script is run before removing any file of the
> package, usually during "ipkg remove".
> In your case, when you have changed make/busybox.mk and
> make/coreutils.mk, you can test by building both packages, and try
> install both ipk files.
> -Brian Zhou