From: Thomas Petazzoni Date: Fri, 24 Jul 2015 11:30:49 +0200 Subject: [Buildroot] [PATCH 03/15] perl-file-listing: fix dependencies In-Reply-To: References: <1437670050-27014-1-git-send-email-francois.perrad@gadz.org> <1437670050-27014-3-git-send-email-francois.perrad@gadz.org> <20150723223922.221466c7@free-electrons.com> Message-ID: <20150724113049.6e556b82@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Fran?ois, On Fri, 24 Jul 2015 11:19:10 +0200, Fran?ois Perrad wrote: > After reading pkg-python.mk, its dependency handling seems complicated to me. Hu? What do you find complicated? It's maybe a bit complicated by the Python 2 vs. Python 3 thing, which you don't have in the Perl world. > By opposite, in Perl infrastructure, it seems trivial: > - in pkg-perl.mk, host-perl is always added as dependency (for target > and host), > - the scancpan script adds perl as dependency only for target package. > > This series contains many dependency fixes because these packages were > hand-written, instead of generated by scancpan. I found these issues > with scancpan when regenerating these packages. I'm sorry, but if there is no reason to have a Perl module on the target without the Perl interpreter, then the dependency on 'perl' should be added automatically by the package infrastructure. Then you simply adjust the scancpan script to *not* add 'perl' to the list of dependencies for each Perl module, and that's it. Can you work on that and respin your patch series accordingly? Thanks! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com