From: Luca Boccassi <bluca@debian.org>
To: Aaron Conole <aconole@redhat.com>, Thomas Monjalon <thomas@monjalon.net>
Cc: Michael Santana <msantana@redhat.com>,
dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [PATCH v5 2/2] ci: Introduce travis builds for github repositories
Date: Wed, 27 Feb 2019 16:06:49 +0000 [thread overview]
Message-ID: <c0e3cf14024389281bf99d14d88725fc9bc1928c.camel@debian.org> (raw)
In-Reply-To: <f7tk1hljkir.fsf@dhcp-25.97.bos.redhat.com>
On Wed, 2019-02-27 at 10:53 -0500, Aaron Conole wrote:
> Thomas Monjalon <thomas@monjalon.net> writes:
>
> > 27/02/2019 15:35, Aaron Conole:
> > > Thomas Monjalon <thomas@monjalon.net> writes:
> > > > 07/02/2019 23:01, Michael Santana:
> > > > > +python3.5 -m pip install --upgrade meson --user
> > > >
> > > > Which distributions have python3.5?
> > > > It looks very specific.
> > >
> > > I agree, could probably just be python3 we need to check and see
> > > if we
> > > can just use that.
> > >
> > > But, we did need the upgrade.
> > >
> > > Travis environment comes up with ubuntu 14.04, which includes
> > > python3.4,
> > > and the requisite version of meson needs python3.5 or higher.
> >
> > It could be a python --version check then?
>
> Well, I don't know what the purpose of the version check would
> be. We
> can tailor the environments. Just need to pass the right
> information,
> that's all. I think we'll make it look nicer, though. We can do any
> environment specific fix ups in the prepare scripts, which I think
> makes
> sense. Then the build script can be a bit more generic.
Travis supports Ubuntu 16.04 images now, which have python 3.5, I'd
suggest to just use them (dist: xenial) so you can skip all the checks
and the manual installations.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-02-27 16:06 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 22:07 [PATCH] Introduce travis builds for github repositories Michael Santana
2019-01-24 9:35 ` Bruce Richardson
2019-01-24 9:41 ` Bruce Richardson
2019-01-24 18:11 ` Aaron Conole
2019-01-24 18:31 ` Bruce Richardson
2019-01-24 18:18 ` Thomas Monjalon
2019-01-24 20:02 ` Aaron Conole
2019-01-24 19:26 ` Honnappa Nagarahalli
2019-01-24 19:51 ` Michael Santana Francisco
2019-01-30 22:16 ` [PATCH v2 0/2] Introduce travis support Michael Santana
2019-01-30 22:16 ` [PATCH v2 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-01-31 9:15 ` Bruce Richardson
2019-01-30 22:16 ` [PATCH v2 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-01-31 9:25 ` Bruce Richardson
2019-01-31 16:43 ` Aaron Conole
2019-01-31 20:32 ` Bruce Richardson
2019-01-31 20:43 ` Aaron Conole
2019-02-01 16:48 ` [PATCH v3 0/2] Introduce travis support Michael Santana
2019-02-01 16:48 ` [PATCH v3 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-02-01 16:48 ` [PATCH v3 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-02-04 9:41 ` Bruce Richardson
2019-02-06 19:17 ` Honnappa Nagarahalli
2019-02-06 20:18 ` Aaron Conole
2019-02-06 22:13 ` [PATCH v4 0/2] Introduce travis support Michael Santana
2019-02-06 22:13 ` [PATCH v4 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-02-06 22:13 ` [PATCH v4 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-02-07 17:16 ` Honnappa Nagarahalli
2019-02-07 22:01 ` [PATCH v5 0/2] Introduce travis support Michael Santana
2019-02-07 22:01 ` [PATCH v5 1/2] examples/vhost_scsi: Don't build without virtio_scsi.h Michael Santana
2019-02-27 14:09 ` Thomas Monjalon
2019-02-07 22:01 ` [PATCH v5 2/2] ci: Introduce travis builds for github repositories Michael Santana
2019-02-27 13:56 ` Thomas Monjalon
2019-02-27 14:35 ` Aaron Conole
2019-02-27 15:23 ` Thomas Monjalon
2019-02-27 15:53 ` Aaron Conole
2019-02-27 16:06 ` Luca Boccassi [this message]
2019-02-27 16:17 ` Aaron Conole
2019-02-14 14:30 ` [PATCH v5 0/2] Introduce travis support Michael Santana Francisco
2019-02-25 18:40 ` Aaron Conole
2019-03-04 16:12 ` [PATCH v6 0/1] " Michael Santana
2019-03-04 16:12 ` [PATCH v6 1/1] ci: Introduce travis builds for github repositories Michael Santana
2019-03-04 18:14 ` Luca Boccassi
2019-03-14 13:21 ` Michael Santana Francisco
2019-03-20 16:01 ` Thomas Monjalon
2019-03-20 19:28 ` Michael Santana Francisco
2019-03-20 21:11 ` Luca Boccassi
2019-03-21 15:45 ` Michael Santana Francisco
2019-03-22 16:56 ` [PATCH v7] " Michael Santana
2019-03-25 15:32 ` [PATCH v8] " Michael Santana
2019-03-25 16:10 ` Thomas Monjalon
2019-03-26 21:54 ` Thomas Monjalon
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=c0e3cf14024389281bf99d14d88725fc9bc1928c.camel@debian.org \
--to=bluca@debian.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=msantana@redhat.com \
--cc=thomas@monjalon.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.