From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Martin Hundebøll" <martin@geanix.com>,
"Khem Raj" <raj.khem@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/9] dos2unix.bbclass: Move to oe-core
Date: Mon, 20 Aug 2018 10:43:02 +0100 [thread overview]
Message-ID: <73a419cb40a67f5e2dfa71820c048645583a1d75.camel@linuxfoundation.org> (raw)
In-Reply-To: <45c972cc-6abf-8df2-e4db-ee84abd49dc9@geanix.com>
On Mon, 2018-08-20 at 11:23 +0200, Martin Hundebøll wrote:
> Hi Khem,
>
> On 19/08/2018 19.23, Khem Raj wrote:
> > - Import from meta-oe layer
> >
> > - This is useful for many packages where CR-LF
> > needs to be adjusted, many recipes depend on it
> > e.g. meta-multimedia libebml and so on.
> >
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > ---
> > meta/classes/dos2unix.bbclass | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> > create mode 100644 meta/classes/dos2unix.bbclass
> >
> > diff --git a/meta/classes/dos2unix.bbclass
> > b/meta/classes/dos2unix.bbclass
> > new file mode 100644
> > index 0000000000..3fc17e2196
> > --- /dev/null
> > +++ b/meta/classes/dos2unix.bbclass
> > @@ -0,0 +1,14 @@
> > +# Class for use to convert all CRLF line terminators to LF
> > +# provided that some projects are being developed/maintained
> > +# on Windows so they have different line terminators(CRLF) vs
> > +# on Linux(LF), which can cause annoying patching errors during
> > +# git push/checkout processes.
> > +
> > +do_convert_crlf_to_lf[depends] += "dos2unix-
> > native:do_populate_sysroot"
>
> Shouldn't the dos2unix recipe live in oe-core also, when a class
> depends upon it?
Not necessarily, we do have a number of core classes which aren't
directly used in OE-Core but are needed by many layers and having a
common copy makes sense.
I'd agree it is good to try and have something which tests them though.
Cheers,
Richard
next prev parent reply other threads:[~2018-08-20 9:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 17:23 [PATCH V2 0/9] Use llvmpile for mesa on x86/x86-64 Khem Raj
2018-08-19 17:23 ` [PATCH 1/9] mesa: Enable gallium-llvm on x86 and x86_64 Khem Raj
2018-08-20 9:40 ` Richard Purdie
2018-08-20 17:14 ` Khem Raj
2018-08-20 17:51 ` Khem Raj
2018-08-19 17:23 ` [PATCH 2/9] powerpc: Remove pie flags from compiler cmdline Khem Raj
2018-08-19 17:23 ` [PATCH 3/9] llvm: Point llvm-config to one built with llvm-native Khem Raj
2018-08-19 17:23 ` [PATCH 4/9] dos2unix.bbclass: Move to oe-core Khem Raj
2018-08-20 9:23 ` Martin Hundebøll
2018-08-20 9:43 ` Richard Purdie [this message]
2018-08-20 17:02 ` Khem Raj
2018-08-20 17:22 ` Khem Raj
2018-08-19 17:23 ` [PATCH 5/9] llvm: Use YOCTO_ALTERNATE_MULTILIB_NAME environment variable in llvm-config Khem Raj
2018-08-19 17:23 ` [PATCH 6/9] mesa: Define YOCTO_ALTERNATE_MULTILIB_NAME to consider multilib names Khem Raj
2018-08-19 17:23 ` [PATCH 7/9] binutils: Update past 2.31.1 release Khem Raj
2018-08-19 17:23 ` [PATCH 8/9] gdb: Upgrade to 8.1.1 Khem Raj
2018-08-20 2:23 ` ChenQi
2018-08-20 2:41 ` Khem Raj
2018-08-20 10:59 ` Richard Purdie
2018-08-20 17:01 ` Khem Raj
2018-08-19 17:23 ` [PATCH 9/9] libidn2: Fix libunistring detection Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73a419cb40a67f5e2dfa71820c048645583a1d75.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin@geanix.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox