From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools
Date: Fri, 10 Mar 2017 11:30:11 -0300 [thread overview]
Message-ID: <CAP9ODKogXP8vO7CCmxs2c-TiRmZZhOKyN5M=ffZV7U2Qrjw1hQ@mail.gmail.com> (raw)
In-Reply-To: <37d4f98c-9102-f4bf-c6cc-f64e1ffbce40@linux.intel.com>
Hello Alexander,
On Fri, Mar 10, 2017 at 10:49 AM, Alexander Kanavin
<alexander.kanavin@linux.intel.com> wrote:
> The new generation of programming languages (think node.js, Go, Rust) is a
> poor fit for the Yocto build model which follows the traditional Unix model.
> In particular, those new development environments have no problem with
> 'grabbing random stuff from the Internet' as a part of development and build
> process. However, Yocto has very strict rules about the build steps and what
> they can and can not do, and also a strict enforcement of license and
> version checks for every component that gets built. Those two models clash,
> and this is a proposal of how they could be reconciled.
When integrating the CHICKEN Scheme support onto the Yocto Project we
dealt it using their installation tool but making the package of
individual packages (eggs, in this specific case) as individual
recipes. We went further and automated the recipe generation and this
made it quite easy to maintain in long term.
Take a look at:
https://github.com/OSSystems/meta-chicken
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2017-03-10 14:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 13:49 Proposal: dealing with language-specific build tools/dependency management tools Alexander Kanavin
2017-03-10 14:30 ` Otavio Salvador [this message]
2017-03-10 14:48 ` [Openembedded-architecture] " Alexander Kanavin
2017-03-10 14:58 ` Otavio Salvador
2017-03-10 15:10 ` Alexander Kanavin
2017-03-10 15:33 ` Derek Straka
2017-03-10 15:35 ` Derek Straka
2017-03-13 8:25 ` Piotr Figiel
2017-03-13 17:51 ` Bruce, Henry
2017-03-16 10:25 ` Alexander Kanavin
2017-03-10 16:23 ` Mark Hatle
2017-03-10 20:37 ` Josef Holzmayr
2017-03-10 20:49 ` Trevor Woerner
2017-03-11 13:07 ` Josef Holzmayr
2017-03-13 20:58 ` Paul Eggleton
2017-03-16 8:17 ` [Openembedded-architecture] Sum up - " Josef Holzmayr
2017-03-16 9:30 ` Paul Barker
2017-03-16 10:35 ` Alexander Kanavin
2017-03-16 10:48 ` Jack Mitchell
2017-03-16 11:42 ` Alexander Kanavin
2017-03-16 11:47 ` Alexander Kanavin
2017-03-16 19:41 ` Patrick Ohly
2017-03-16 15:45 ` Mark Hatle
2017-03-16 15:43 ` Mark Hatle
2017-03-16 10:21 ` Alexander Kanavin
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='CAP9ODKogXP8vO7CCmxs2c-TiRmZZhOKyN5M=ffZV7U2Qrjw1hQ@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=yocto@yoctoproject.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.