Am 30.03.2012 21:25, schrieb Andrew:
> Hi all.
> Today I realized my idea of automation of package definition for initrd 
> and moddb for each arch. It looks for me tiny and clear for 
> understanding/modifying.
> Now there are template file with ##ARCH## tag and other files except 
> kernel modules, and list of regexps for module names that are required 
> for that package.
> It seems that nothing was forgotten in that operation - just removed 
> some rarely-used modules; and some modules that are prerequisites for 
> currently present in moddb were added in that way, + added some 
> iptables-related and IPVS modules.
> So it waits testing, and now it seems that all environment is prepared 
> for experiments in cross-compilation.

Hi Andrew;

pls look into my previous mail, how much I enjoy the/your work for
cross-compiling.

While I'm convinced that your approach works and is tiny, I'm not shure
if it's "understandable". I looked a long time in to your changes and my
impression is that you've "over-simplified" it.

The logic to build the files for buildpacket.pl has been put into
buildtool.mk, the file to declare the modules is really simple. Anyway
it breaks the "rules" how to define the filelist for packages.
So it's different compared to any other package. While the current
approach is "stupid", it just works and until today it's always the same
for every package.

I'm afraid that putting the logic into buildtool.mk , and to make a
difference in package definitions requires more documentation, raises
questions and is in fact not as easy to understand as we like.

If it's really necessary for cross-compiling I'll swallow it, if not I'd
like to go with the common approach, just to keep it as simple as
possible over the whole buildtool setup.

opinions?
kp

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to