All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>, Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] wget: inherit perlnative
Date: Mon, 25 Jan 2016 18:01:11 +0800	[thread overview]
Message-ID: <56A5F267.3090608@windriver.com> (raw)
In-Reply-To: <CAJTo0LYrOjAaOALMkon02aJNrDL43dNgJ6s2G=aPhtejodQwMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

On 2016年01月25日 16:48, Burton, Ross wrote:
>
> On 25 January 2016 at 07:27, Khem Raj <raj.khem@gmail.com 
> <mailto:raj.khem@gmail.com>> wrote:
>
>     what happens for wget-native ? Does it now serialize the build ?
>
>
> Thankfully wget-native is an assumed dependency (albeit not 
> explicitly, we should fix that).
>
> But I do agree that perlnative is a *huge* dependency for a bit of 
> documentation.  SLED 11 is rather old now (released 2009), we don't 
> test it on the autobuilders, and support for it ends in less than two 
> months.  I'd prefer to either call this a distro patch for products 
> who want to continue to support SLED11, or patch the documentation 
> build so that it doesn't pass --utf8 if that isn't harmful.

If oe-core doesn't support SLED11, I'll make this as a local commit. 
When the support for SLED11 ends, it could be removed easily.

Thank you all.

--Kai


>
> Ross


-- 
Regards,
Neil | Kai Kang


[-- Attachment #2: Type: text/html, Size: 2609 bytes --]

      reply	other threads:[~2016-01-25 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  6:44 [PATCH 0/1] Add dependency perl-native for wget kai.kang
2016-01-25  6:44 ` [PATCH 1/1] wget: inherit perlnative kai.kang
2016-01-25  7:27   ` Khem Raj
2016-01-25  8:48     ` Burton, Ross
2016-01-25 10:01       ` Kang Kai [this message]

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=56A5F267.3090608@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=ross.burton@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.