[Buildroot] [UNSURE]Re: [PATCH 5/6] intltool: refactor with host-perl

["François Perrad" <francois.perrad@gadz.org>]

2014-10-06 17:37 GMT+02:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
> Dear Fran?ois Perrad,
>
> On Wed, 20 Aug 2014 18:45:07 +0200, Fran?ois Perrad wrote:
>
>> host-intltool depends on host-perl-xml-parser,
>> and now, host-perl-xml-parser depends on host-perl.
>>
>> A host-perl-foo-module cannot depend on host-perl OR system-perl.
>> All host-perl-foo-module must depend on host-perl.
>
> Sorry, but it's not acceptable to have host-intltool depend on
> host-perl. It's bringing a huge dependency (host-perl) in a large
> number of configurations, since host-intltool is used by so many
> packages.
>
> I had a discussion with Gustavo about this not long ago, and here is
> our proposal: change host-perl-xml-parser to *not* use the perl package
> infrastructure, as an exception. This way, it will not depend on
> host-perl, and we'll be happy. Of course, it's a bit ugly because we
> have a Perl package not handled by the package infrastructure, but
> that's a reasonable solution for this problem.
>

Ok, I'll experiment this proposal.

Fran?ois

> Another approach would be to make host-intltool not depend on
> XML::Parser. It seems like it's possible to get rid of the XML::Parser
> dependency by passing no-xml as the second argument of the
> IT_PROG_INTLTOOL macro. But this needs to be done in each and every
> package using intltool. All of the packages that are not using XML
> based translation files could pass no-xml, and we would get rid of the
> dependency on host-perl-xml-parser for those packages. That could be
> one option.
>
> Since the vast majority of projects seem to be using "ini style"
> translation files, we could probably use no-xml on many of them and get
> rid of the problem.
>
> Thoughts?
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com