All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Zhang <sen.zhang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: should perl modules go in oe-core? (possibly python and ruby ones too)
Date: Thu, 16 May 2013 14:56:07 +0800	[thread overview]
Message-ID: <51948307.5070608@windriver.com> (raw)

Hi,

We've accumulated quite a few perl modules and would like to contribute
some/all of them to oe-core. But I think we'd better ask how everyone
thinks before doing so, since the number of the modules are pretty
large, and the policy may as well apply to python/ruby packages.

Most of the modules are simple cpan recipes. They are easy to maintain,
but do consume *some* manpower.

I think there are a few alternatives.

1. decide on each module on a case-by-case basis.

2. keep all of them in some special layer other than oe-core.

3. everyone maintain what they need in-house.

None of them seems perfect. Is there already some policy?

jesse



             reply	other threads:[~2013-05-16  7:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  6:56 Jesse Zhang [this message]
2013-05-16  9:40 ` should perl modules go in oe-core? (possibly python and ruby ones too) Richard Purdie
2013-05-16 11:13 ` Phil Blundell
2013-05-16 11:37 ` Joe MacDonald

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=51948307.5070608@windriver.com \
    --to=sen.zhang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.