From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] support/docker: sort the list of installed packages
Date: Sun, 3 Jun 2018 09:24:07 +0200 [thread overview]
Message-ID: <20180603072407.GB23330@scaer> (raw)
In-Reply-To: <5b136cda73b5f_208c3fee3611587852799@ultri5.mail>
Ricardo, All,
On 2018-06-03 01:21 -0300, Ricardo Martincoski spake thusly:
> On Sat, Jun 02, 2018 at 07:19 PM, Yann E. MORIN wrote:
> > RUN apt-get install -y --no-install-recommends \
> > - build-essential cmake libc6:i386 g++-multilib \
> > - bc ca-certificates file locales rsync \
> > - cvs bzr git mercurial subversion wget \
> > - cpio unzip \
> > + bc \
> > + build-essential \
> > + bzr \
> > + ca-certificates \
> > + cpio \
> > + cvs \
> > + file \
> > + g++-multilib \
> > + git \
> > + libc6:i386 \
> > libncurses5-dev \
> > - python-nose2 python-pexpect qemu-system-arm qemu-system-x86 \
> > - python-pip && \
>
> With only patches 1 and 2 applied the 'docker build' command will fail:
> /usr/bin/python: No module named pip
Oooh dang... I missed that one when doing the interactive git-add...
> This removal should be part of patch 4.
Obviously so, yes.
> > + locales \
> > + mercurial \
> > + python-nose2 \
> > + python-pexpect \
> > + qemu-system-arm \
> > + qemu-system-x86 \
> > + rsync \
> > + subversion \
> > + unzip \
> > + wget \
> > + && \
>
> We usually don't put && in a separate line.
> I am not really against it if no one else complains.
Well, I'm not too sure either. We have two coflicting rules here:
- one package per-line, so that we can add/remove packages without
touching the existing lines, so if we were top add a package after
the last one, we'd have to touch two lines,
- we almost exclusively put the && at the end of a line...
Note that the docker best practices put the && at the beginning of the
line when they need to split lines.
So, I don't care what rule we apply (as I prefer neither, as I favour
the one in the docker best practices).
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-06-03 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 22:19 [Buildroot] [PATCH 0/4] support/docker: make the image more reproducible Yann E. MORIN
2018-06-02 22:19 ` [Buildroot] [PATCH 1/4] support/docker: run apt-get update and apt-get install in two RUNs Yann E. MORIN
2018-06-03 4:20 ` Ricardo Martincoski
2018-06-02 22:19 ` [Buildroot] [PATCH 2/4] support/docker: sort the list of installed packages Yann E. MORIN
2018-06-03 4:21 ` Ricardo Martincoski
2018-06-03 7:24 ` Yann E. MORIN [this message]
2018-06-02 22:19 ` [Buildroot] [PATCH 3/4] support/testing: fix python syntax Yann E. MORIN
2018-06-03 4:24 ` Ricardo Martincoski
2018-06-03 7:11 ` Yann E. MORIN
2018-06-02 22:19 ` [Buildroot] [PATCH 4/4] support/docker: use the distro-provided flake8 Yann E. MORIN
2018-06-03 4:50 ` Ricardo Martincoski
2018-06-03 7:36 ` Yann E. MORIN
2018-06-04 3:38 ` Ricardo Martincoski
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=20180603072407.GB23330@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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.