From: germain <olivier.germain1212@gmail.com>
To: yocto@yoctoproject.org
Subject: [Yocto installation] Yocto installation on corporate environment
Date: Fri, 21 Nov 2014 07:54:04 +0100 [thread overview]
Message-ID: <546EE18C.8090808@gmail.com> (raw)
Hi All,
I am looking for some feedback on yocto distribution installation and
deployment into corporate environment.
The context is the following: We will receive a commercial yocto
distribution from a third party in form of a CD/DVD every year with some
cumulative patches every months. This distribution will be used by
different projects within the company to make products
My concern is how to share/distribute this distribution with the
following objectives:
- Secure all dependencies on corporate network for product maintenance
purpose
- Easily access and installation of a given revision of the distribution
- Control disk space and avoid each project to duplicate the
distribution support
- Avoid lock down effect on third-party proprietary installation mechanism
I though about the following possibilities
1) Mirror all source code URLs including tarball delivery onto
corporate network
=> very costly, need to support all reference type of version control
system(Git, SVN, ....)
=> risk to miss mirroring one url
2) Put in source control (Git) the content of the "Downloads" directory
create by yocto
=> single Git may be very heavy with lot of binaries
=> Split Git but need then to use something to manage the forest like
google repo tool
3) Rely on docker image and create a new version of docker image for
each new distribution revision
=> working on a shell inside the docker image may be not much easy
since need to rely on external volumes to access user personal data or
environment
Thanks in advance for your return
BR
Olivier
reply other threads:[~2014-11-21 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=546EE18C.8090808@gmail.com \
--to=olivier.germain1212@gmail.com \
--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.