Hi. Maybe we should add 'lwp' buildtool package type for lwp like for initrd?
06.12.2014 13:41, Erich Titl пишет: > Hi KP > > Am 06.12.2014 um 09:13 schrieb kp kirchdoerfer: >> Hi Erich; >> >> Am Freitag, 5. Dezember 2014, 22:13:01 schrieb Erich Titl: >>> Hi KP >>> >>> I have not been able to understand why the lwp generation is so >>> different in every aspect from the generation of 'normal' packages. >>> Where is the logic for the lwp generation hidden, it definitely does not >>> have a buildtool.cfg which takes care of the package generation. >> It's in repo/weboconf/buildtool.cfg (the basic stuff) and in buildlwp.sh (for >> package-related web configuration files). >> >>> As there is no compilation involved would it not make most sense to just >>> put this logic into the buildtool.mk for lwp? >> buildtool.cfg for lwp would be a better place to generate the packages >> instead >> buildlwp.sh indeed. > As they are quite simple a target in buildtool.mk would suffice and not > disturb the generic buildtool structure. > > .. >> Yes I have been quite strict in my opinion, sorry for that. >> But as it is, it will be also easy to replace the whole webconf stuff >> without >> changing the corresponding leaf packages. >> >> hth > A bit but not that much as it still leaves lwp in a quite unordered > state. The way .lwp packages are built, they are just a gzipped tarball > of a few files, all strictly sources. IMHO it does not make much sense > in the buildtool process to extract files from a tarball to build > sources to just compine the same content with the same tools. So we > could very much simplify the process by just providing the tarballs in > repo/lwp. > > I had a look in repo/lwp as I did not know where the various parts of > the existing webconf were dispersed and I found it grossly overcoded to > have first a flat file structure which then was dispersed in various > directories just to be but together by an external script to the general > buildtool process. All these steps look completely redundant to me. > > I will add wpasupp.lwp to the build process in a consistant way hoping > not to fall into the same tarpit. We'll see. > > cheers > > Erich > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > > > _______________________________________________ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
