From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Paolo Pisati <paolo.pisati@canonical.com>
Cc: "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, 8 Dec 2017 00:31:28 +0900 [thread overview]
Message-ID: <CAK7LNARWZ-OSV+USgzuQCK4H1UL3pvY-NRDVN2665tuaOgqkSA@mail.gmail.com> (raw)
In-Reply-To: <CAMsH0TSzcWYV5tru7NXDOur_pHNHO+qkEgpp0m--Jeqjn-h7KQ@mail.gmail.com>
2017-12-07 3:14 GMT+09:00 Paolo Pisati <paolo.pisati@canonical.com>:
> On Wed, Dec 6, 2017 at 11:36 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>> Just one question to Paolo:
>>
>> If some change like firmware removal happens in the future,
>> patching for snapcraft is necessary?
>> (i.e. users are required to upgrade snapcraft from --edge ?)
>>
>> I guess the answer is yes, because "plugin: kernel" needs to know
>> the kernel-build system internal.
>
> Well, in this case, i had to fix the 'kernel-with-firmware' option to
> skip the 'firmware_install' step since
> we took it by default - let's say that in the future the
> 'modules_install' target is removed or change name,
> then i'll have to patch snapcraft.
>
> Wrt updating from -edge, i told you to take it from there because snap
> packages land there more often and more quickly
> compared to the canonicaldeb archive, so from a developer perspective
> it's easier&quicker to iterate over it, but sooner
> or later (e.g. once snapcraft 2.36.1 reaches the snap -stable
> channel), it will be copied to the deb archive too -
> IOW, you would get using apt-get only too.
> --
I will pick up this for v4.16-rc1.
It sounds like this target is a bit fragile, but let's see.
I hope a breakage will not happen...
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2017-12-07 15:32 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 [this message]
2017-12-12 15:08 ` Masahiro Yamada
2017-12-01 12:03 ` Riku Voipio
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=CAK7LNARWZ-OSV+USgzuQCK4H1UL3pvY-NRDVN2665tuaOgqkSA@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--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 \
/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).