From: Riku Voipio <riku.voipio@linaro.org>
To: Paolo Pisati <paolo.pisati@canonical.com>
Cc: "Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Jim Davis" <jim.epost@gmail.com>,
"Michal Marek" <michal.lkml@markovi.net>,
"Behan Webster" <behanw@converseincode.com>,
"Matthias Kaehlcke" <mka@chromium.org>,
"Vinícius Tinti" <viniciustinti@gmail.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] scripts/package: snap-pkg target
Date: Fri, 1 Dec 2017 14:03:31 +0200 [thread overview]
Message-ID: <CAAqcGHmG7jNvWXbG7_FTpLb4FrD5BjDfzzQMXqu7s9hvwnXUYw@mail.gmail.com> (raw)
In-Reply-To: <CAMsH0TRSnWvR8pH-3ksBsb-WPMuq-PpFT+W6PdBX=xd-HhyZ4g@mail.gmail.com>
On 29 November 2017 at 19:05, Paolo Pisati <paolo.pisati@canonical.com> wrote:
> On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>>
>> Worked for me too,
>> after updating snapcraft.
>>
>>
>> Is it really impossible to check the snapcraft version?
>> What is the minimum version? 2.35 ?
>
> The minimum version is 2.35+ - what is about to become 2.36 anytime soon now.
Since you are already patching snapcraft for this, why not embed the
whole support in snapcraft? Eg something like snapcraft --kernel
/path/to/kernel
The key advantage you'll get is being able to support old kernel versions too.
Riku
next prev parent reply other threads:[~2017-12-01 12:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171114123834.xsjiy2ynvott4gae@brain>
2017-11-27 11:07 ` [PATCH v3] scripts/package: snap-pkg target Paolo Pisati
2017-11-27 18:33 ` Jim Davis
2017-11-28 17:14 ` Paolo Pisati
2017-11-28 19:35 ` Jim Davis
2017-11-29 7:33 ` Masahiro Yamada
2017-11-29 17:05 ` Paolo Pisati
2017-11-30 23:15 ` Jim Davis
2017-12-05 11:43 ` Paolo Pisati
2017-12-05 21:23 ` Jim Davis
2017-12-06 10:36 ` Masahiro Yamada
2017-12-06 18:14 ` Paolo Pisati
2017-12-07 15:31 ` Masahiro Yamada
2017-12-12 15:08 ` Masahiro Yamada
2017-12-01 12:03 ` Riku Voipio [this message]
2017-12-05 11:31 ` Paolo Pisati
2017-11-29 17:03 ` Paolo Pisati
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=CAAqcGHmG7jNvWXbG7_FTpLb4FrD5BjDfzzQMXqu7s9hvwnXUYw@mail.gmail.com \
--to=riku.voipio@linaro.org \
--cc=behanw@converseincode.com \
--cc=jim.epost@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mka@chromium.org \
--cc=paolo.pisati@canonical.com \
--cc=viniciustinti@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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;
as well as URLs for NNTP newsgroup(s).