Am Montag, 28. September 2015, 19:08:32 schrieb Erich Titl: > Am 28.09.2015 um 17:48 schrieb kp kirchdoerfer: > > Hello Erich; > > > > Am Sonntag, 27. September 2015, 13:55:34 schrieb Erich Titl: > >> Hi KP > >> I checked the contents of the 5_2 directory this morning using > >> build_upgrade > >> > >> running build_upgrade with parameters 5.2.x 5_2 > > > > while this is fine for testing, we'll need more work for a comprehensive > > solution within the build process. > > As I said before, some of the packages are committed from packages > > directory, the kernel from build dir and some finally from the images. > > This requires a lot of manual intervention and should be improved. > > Ideas welcome. > > 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 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 buildimages.pl as documented in the Developer Guide. > - After a full build and packages build all the packages for each > release should be in the packages directory and can just be copied Not all, there is some mangling in buildimages... > - 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? I'd like to see this handled by upgrade script on the router. kp > Building the installation images is a slightly more complex process and > I have no information on how it is done, but then I did not read the > complete developers manual. > > > ... > > > Currently the firmware.tgz needs user intervention. > > One can unpack firmware and copy required files to /lib/firmware and then > > they'll saved with lrcfg... > > I will keep firmware.tgz as is for now but unpacking it to a directory > above to be able to build a current moddb. That is the way upgrade was > designed. > > > To support more automagic integration AFAIK we need either to enhance > > modules or to come up with a new config file. Or something else. > > > >> Also I believe we can remove the stable-test directory and, to be > >> honest, I am not sure we need to conserve 3_1 and 4_0. > > > > stabble-test has been what it says - a branch you've created for testing. > > OK, I get rid of it > > > I agree we don't need 3_1 and 4_0 any longer, but IMHO it doesn't hurt to > > keep as-is. > > No sweat, just a question of storage. > > cheers > > ET > > > > ---------------------------------------------------------------------------- > -- > > _______________________________________________ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------------------------------ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
