From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 8 Oct 2012 21:13:25 +0200 Subject: [Buildroot] [PATCH v9 02/10] perl: new package In-Reply-To: References: <1349531633-26717-1-git-send-email-francois.perrad@gadz.org> <1349531633-26717-2-git-send-email-francois.perrad@gadz.org> <20121008113433.4b4bcc1b@skate> <20121008134900.403178cf@skate> Message-ID: <20121008211325.3138bc79@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Mon, 8 Oct 2012 18:56:09 +0200, Fran?ois Perrad wrote: > a BR user could choose between 2 methods for installing Perl : > - a full install supplied by the script `installperl` from the Perl tarball > - a custom install which reproduce the behavior of the BR package of microperl, > where the user explicitily defines each module/file to install > > In my sense, when a user chooses the full install, he must also use > the post-build script which removes its useless files, > like CORE/*.h or the Unicode support. This is in complete contradiction with what we do in all other Buildroot packages, so I don't think your statement actually makes sense in the context of Buildroot. Unless BR2_HAVE_DEVFILES is enabled, we don't want development files to be installed on the target. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com