From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 5/7] support/dockerfile: install flake8
Date: Wed, 30 May 2018 17:36:18 +0200 [thread overview]
Message-ID: <20180530153618.GB2592@scaer> (raw)
In-Reply-To: <5b0ccc753f59_1c272ab87ea319a052883@ultri5.mail>
Ricardo, All,
On 2018-05-29 00:43 -0300, Ricardo Martincoski spake thusly:
> On Mon, May 28, 2018 at 04:44 PM, Yann E. MORIN wrote:
> > Why do we even use pip to install those? Can't we just rely on the
> > verions actually packaged in the distro instead? I.e.
[--SNIP--]
> >> Are you preparing a patch?
> > When we agree on the directions, yes I can.
>
> Reproducible images with less code and less maintenance effort in exchange of
> using a not-so-bleeding-edge version. Makes sense to me.
OK, so I'll send a patch to implement this soilution.
Thanks! :-)
> I am only in doubt how future-proof is this solution, if some day we will
> *need* a new version, i.e. to something related to Python3 in 2020 (it's only a
> wild guess!, I don't know any current limitation, I don't know the internals of
> flake8).
> But then probably debian will have a newer version of flake8, so we can update
> the stretch version. And we can always go back to using pip if really needed.
Yes, then we can update to a newer version of the distro.
There was also a wild suggestion that we provide more Docker images,
for each of the mainstream distros.
Because sometimes, build issues only occur on some distros and not
others, e.g. arch-linux, which uses musl, sometimes break the build of
some host packages, and it is difficult to diagnose and fix...
I was also looking into providing additional Dockerfiles for additional
distros. I'll get this in the same series. Soon. Sooooon.... ;-)
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-05-30 15:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 3:09 [Buildroot] [PATCH v3 0/7] fix Python code style v3 Ricardo Martincoski
2018-03-13 3:09 ` [Buildroot] [PATCH v3 1/7] genrandconfig: fix code style Ricardo Martincoski
2018-03-13 21:27 ` Peter Korsgaard
2018-03-13 3:09 ` [Buildroot] [PATCH v3 2/7] size-stats-compare: " Ricardo Martincoski
2018-03-13 21:27 ` Peter Korsgaard
2018-03-13 3:09 ` [Buildroot] [PATCH v3 3/7] test_python_cryptography: " Ricardo Martincoski
2018-03-13 7:39 ` Yegor Yefremov
2018-03-13 21:32 ` Peter Korsgaard
2018-03-13 3:09 ` [Buildroot] [PATCH v3 4/7] scanpypi: " Ricardo Martincoski
2018-03-13 7:39 ` Yegor Yefremov
2018-03-13 21:32 ` Peter Korsgaard
2018-03-13 3:09 ` [Buildroot] [PATCH v3 5/7] support/dockerfile: install flake8 Ricardo Martincoski
2018-03-13 17:22 ` Yann E. MORIN
2018-03-13 21:37 ` Peter Korsgaard
2018-05-27 16:42 ` Yann E. MORIN
2018-05-28 3:00 ` Ricardo Martincoski
2018-05-28 19:44 ` Yann E. MORIN
2018-05-29 3:43 ` Ricardo Martincoski
2018-05-30 15:36 ` Yann E. MORIN [this message]
2018-03-13 3:09 ` [Buildroot] [PATCH v3 6/7] .gitlab-ci.yml: check flake8 Ricardo Martincoski
2018-03-13 18:15 ` Yann E. MORIN
2018-03-14 23:16 ` Ricardo Martincoski
2018-03-18 16:25 ` Yann E. MORIN
2018-03-30 21:12 ` Yann E. MORIN
2018-03-30 22:38 ` Ricardo Martincoski
2018-03-31 20:49 ` Thomas Petazzoni
2018-03-13 3:09 ` [Buildroot] [PATCH v3 7/7] .flake8: ignore utils/diffconfig Ricardo Martincoski
2018-03-13 21:38 ` Peter Korsgaard
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=20180530153618.GB2592@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox