Re: [yocto] multiconfig samples not put in the build dir.

2017-04-12 Thread Paulo Neves
>Not really my call to make. Also, please keep this discussion on the >mailing list so that everyone benefits. Sorry forgot to hit the reply all. Thanks for the suggestion I am now waiting input from the rest of the community regarding the applicability of rename command. On Wed, Apr 12, 2017 at

Re: [yocto] multiconfig samples not put in the build dir.

2017-04-12 Thread Gary Thomas
On 2017-04-12 09:15, Paulo Neves wrote: Hello Gary. I didn't know it was not a coreutil. To do it in another way i think this simple code will grow. Before refactoring could I have other opinions? We have a very limited environment and even so the rename exists. It is part of the util-linux-ng

Re: [yocto] multiconfig samples not put in the build dir.

2017-04-12 Thread Gary Thomas
On 2017-04-12 09:02, Paulo Neves wrote: I expect it to rename all the .conf.sample files from .conf.sample to .conf. Give it a try ;) This introduces a new dependency for the rename tool/program which is a Perl script. It seems to me that much effort has been made recently to minimize these sc

Re: [yocto] multiconfig samples not put in the build dir.

2017-04-12 Thread Paulo Neves
I expect it to rename all the .conf.sample files from .conf.sample to .conf. Give it a try ;) On Wed, Apr 12, 2017 at 8:54 AM, Gary Thomas wrote: > On 2017-04-12 08:48, Paulo Neves wrote: >> >> Hello, >> >> I thought it would be consistent to have the multiconfig samples to >> also be populated j

Re: [yocto] multiconfig samples not put in the build dir.

2017-04-11 Thread Gary Thomas
On 2017-04-12 08:48, Paulo Neves wrote: Hello, I thought it would be consistent to have the multiconfig samples to also be populated just like the local.conf. I produced a patch accordingly: From 6091978f666463c46093203b74f28b82a9bf4d47 Mon Sep 17 00:00:00 2001 From: Paulo Neves Date: Mon,