First, congrats to the OpenWrt Team on the first public release of Kamikaze 7.06.

One thing is obvious - lack of staple packages I've become accustomed to in Whiterussian.  The first examples were ntpclient and OpenVPN.  NO PROBLEMS getting them loaded - I just pointed to the Whiterussian package and hacked a startup.  If I missed something, please let me know.

These packages are surely not in the Broadcom-on-2.6-kernel category - this stuff is known to be work-in-progress.

Is this oversight?  Are more packages coming?  Should we expect less of ready-to-go Kamikaze packages (compared to Whiterussian)?

TIA

Bill

(Last edited by Bill_MI on 4 Jun 2007, 02:53)

If your building from svn, you can 'make package/symlinks' to bring in all the available packages.  I'm not sure otherwise...

I've been using kamikazee and the buildroot-ng for a long long time now.  Theres a lot of packages in whiterussian that were packaged a long long time ago and subsequently abandoned, and will likely never make it into Kamikazee until someone decides to manually port the package themself.  For it to be a working package with kamikazee, it must be a package which can build under kamikazee.  As of now, there are no backports of old whiterussian binaries to run under kamikazee, nor do I see a demand for making such a hackish repository.

Kamikazee's new buildroot-ng build system is very powerful and much easier than the old whiterussian, but there's not a good automated way for the team to import all the old whiterussian buildfiles unfortuantely, simply too much has changed.  The end of the line is, if you need it (re-)packaged, try packaging itself, and people here will be as best of assistance as they can to help you make new packages.

(Last edited by Rektide on 4 Jun 2007, 03:57)

Official binary packages for optional software will come in time; 7.06 is the first version of Kamikaze, wait for the dust to settle before switching if you desire official packages.  As mentioned above, you can build your own if you are on Linux, BSD, or most other *nix operating systems.  I think the x-wrt team also has a repository of binary packages, but keep in mind that while these packages (typically) use the official makefiles, they are not official binary packages.

Thanks netprince, but my question is more global in nature.  The only thing I've ever had to build in Whiterussian was my own fix for sta mode in wificonf.  The Whiterussian package repository is complete and solid.

Perhaps because the Whiterussian repository evolved over several years Kamikaze just needs to catch up a bit.  The exclusion of ntpclient in the repository looked like an oversight since most supported hardware doesn't even have battery clocks.

EDIT: Rektide, Bartman... thanks for the insight.  But I think you'll agree there's a bit more need for an ntpclient need than the packages that have been abandoned.

(Last edited by Bill_MI on 4 Jun 2007, 04:10)

Actually, most  (if not all) software officially available for White Russian was ported to Kamikaze a long time ago.   The White Russian backports are nothing more than Kamikaze package makefiles built with the White Russian SDK.  Only makefiles for packages required for the proper operation of devices are in the Kamikaze directories (in the svn tree) by default.  The rest are located in the packages dir (all this info is on https://dev.openwrt.org) and as noted above the `make packages/symlinks' command can be used to automatically populate the package/ dir in your local copy of the kamikaze tree.  You can then build the packages you need easily.

As noted above, only the packages required for the devices to work are included.  Everything else will come later.

Thanks.  One thing I'm seeing...

Do most that build their own always strive to get what they need in squashfs then only use jffs2 for confs?  I see the obvious advantage.  Packages via ipkg are not as important - except to us turn-key dabblers.

EDIT: To clarify.  When you include packages that way do they end up nicely compressed in the squashfs image or still separate?

My building experience is limited to HowTos and when I've tried to go further I ended up with a zillion cross-compiling headaches.

(Last edited by Bill_MI on 4 Jun 2007, 04:30)

Many of us do build our own images to save space.  Squashfs compression is significantly better than JFFS2 compression.  A few of us also do it to produce turnkey images of our own (image has most of our configs included in the squashfs partition.)  Some of us also produce our own svn builds because we are using devices that are not fully supported yet, or are helping add support or bug test new functionality.  Others build their own packages because they add custom patches; there are all kinds of reasons.

As I said, X-Wrt does have binary packages if you want something right now, but keep in mind that they are not official OpenWrt packages.

Contrary to what is written above. Packages are something we want to supply public trees for. However as Kamikaze is a fast moving target and packages are quite frankly a lot of work, they aren't going to be released overnight. A process of fixing them up ready for release, but if you can't wait then you can compile them using the SDK.
TTFN

Mike

The brcm-2.4 target has been updated to include all of the packages.

Thanks, mbm.  WOW!  That's more packages than Whiterussian ever had in the repository at first glamce.

And thanks to everyone for all the info.

EDIT:  Holy cow... I'm not kidding...

Public Package repository.
  Whiterussian 0.9: 361
  Kamikaze 7.06 (before): 159
  Kamikaze 7.06 (after): 769

(Last edited by Bill_MI on 4 Jun 2007, 12:05)

Sorry for the thread revival. But it seems that this is what I'm after.

At the moment I really don't have the time to switch to Kamikaze (still using WhiteRussian) - but I'd really need some of the packages from it.
When compiling with the Kamikaze buildroot they won't work with WhiteRussian ("not found" error)
It seems that the structure of those Kamikaze makefiles is really different and I do not have enough experience in writing makefiles

So, could somebody please tell me how to compile the Kamikaze makefiles with the WhiteRussian SDK?

[edit] Nevermind... seems like I'll have to switch over to Kamikaze for what I want to do

(Last edited by simba87 on 16 Mar 2008, 18:51)