On Tue, Dec 10, 2013 at 05:23:29PM +0700, grozin@gentoo.org wrote:
> On Tue, 10 Dec 2013, Chema Alonso wrote:
> > I tested it on an stable amd64 system, no problems found apart from some
> > 'cosmetic' warnings found by repoman:
> >
> >  ebuild.minorsyn               12
> >   dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 50
> >   dev-lisp/sbcl/sbcl-1.0.55-r1.ebuild: Ebuild contains leading spaces on line: 62
> >   dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 51
> >   dev-lisp/sbcl/sbcl-1.0.55-r2.ebuild: Ebuild contains leading spaces on line: 64
> >   dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line: 57
> >   dev-lisp/sbcl/sbcl-1.1.10.ebuild: Ebuild contains leading spaces on line: 70
> >   dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line: 57
> >   dev-lisp/sbcl/sbcl-1.1.11.ebuild: Ebuild contains leading spaces on line: 70
> >   dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line: 57
> >   dev-lisp/sbcl/sbcl-1.1.12.ebuild: Ebuild contains leading spaces on line: 70
> >   dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line: 56
> >   dev-lisp/sbcl/sbcl-1.1.14.ebuild: Ebuild contains leading spaces on line: 69
> >
> > These are easy to fix though =)
> >
> > Will you take care of them?
> These lines are not in the ebuilds proper, but in lisp code embedded into 
> ebuilds. I think it makes no sense to fix them.
> 
> Andrey
> 

Changing them to tabs makes the warnings go away and respects the look
of the lisp code.