Hi KP Am 30.09.2015 um 16:45 schrieb kp kirchdoerfer: > Am Montag, 28. September 2015, 19:08:32 schrieb Erich Titl: ...
>> >> Well, I did not want to interfere with the current set up although I >> _believe_ it is incoprehensibly complicated. That is why I wrote a tool >> to juggle the content to match a more conventional aproach. > > It does not work that way with the tools we have. I don't want to mix up the existing tools. The build_upgrade script just makes the structures more convenient, simpler and easier to handle automatically as the originals hold some unnecessary and puzzling information. > >> I am not familiar with the tools you use to build the images but stuff >> like that should be completely automatic. I would use a makefile, but >> then I am old fashioned. One thing I would _not_ do is write my own file >> management. > > The I use are: > buildpacket.pl Buildpacket.pl just builds packages, no need to do anything about it now. > buildimages.pl Never used it, as I never built an image, but these images need to be copied somewhere anyway. Does buildimage take care of that? Does buildmage handle all the dependencies of the image, e.g. does it build the code and package if it is missing? ... > Not all, there is some mangling in buildimages... That is fine as long as we know about the mangling. But this only affects the images. In the packages repository we don't have images. How do you copy the packages to the package repository? > >> - The kernel and associated modules and initrd files can simply be >> copied to the respective directories. > > see above > >> - The firmware tarball can just be copied, right now I am unpacking it >> in build_upgrade, but this could be done before. > > Why should we start to unpack files, we've packaged before? Because as a package they are inconvenient. I can do it on the fly in upgrade if that bothers you, but this is unnecessary cycles on small systems, unnecessary space requirements on possibly small systems, unnecessary copying of unused code e.t.c. > I'd like to see this handled by upgrade script on the router. see above... normally there is very little content from firmware to be used on a router. Most of firmware is unused code which I would like to avoid to copy over the net. The original taballs still exist, and anyway, the original structures still exist in master as they are untouched. cheers ET ------------------------------------------------------------------------------ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
