Re: [PATCH v5 2/4] deb-pkg: split debug symbols in their own package

[Anisse Astier <anisse@astier.eu>]

On Sat, 15 Jun 2013 05:03:15 +0100, Ben Hutchings <ben@decadent.org.uk> wrote :

> On Fri, 2013-06-14 at 11:46 +0200, Anisse Astier wrote:
> > This can reduce almost 3 times the size of the linux-image package,
> > while keeping the debug symbols available for this particular build, in
> > their own package.
> > 
> > This mimics the way kernels are built in debian, ubuntu, or with
> > make-kpkg, and comes at the price of a small slowdown in the building of
> > packages.
> [...]
> > @@ -128,6 +136,20 @@ if grep -q '^CONFIG_MODULES=y' $KCONFIG_CONFIG ; then
> >  		mv "$tmpdir/lib/modules/$version"/* "$tmpdir/usr/lib/uml/modules/$version/"
> >  		rmdir "$tmpdir/lib/modules/$version"
> >  	fi
> > +	if [ -n "$BUILD_DEBUG" ] ; then
> > +		(
> > +			cd $tmpdir
> > +			for module in $(find lib/modules/ -name *.ko); do
> [...]
> 
> Can shells generally cope with the list this produces for, say, an
> allmodconfig build?  My instinct would be to use xargs and while, but
> I'm willing to believe that this does work.

Did a quick test with an allmodconfig. It has 4038 modules. I'm pretty
sure it should work.

In bash 4.2.37, "for i in $(seq 50000000); do  :; done" does work,
although it ends up eating 5GB of memory.

Anisse