[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMsH0TTtpGE5G-OQLrc_Dk54CRzT9WcF9iUkEB-1=cJ1_oXwqQ@mail.gmail.com>
Date: Tue, 5 Dec 2017 12:31:04 +0100
From: Paolo Pisati <paolo.pisati@...onical.com>
To: Riku Voipio <riku.voipio@...aro.org>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Jim Davis <jim.epost@...il.com>,
Michal Marek <michal.lkml@...kovi.net>,
Behan Webster <behanw@...verseincode.com>,
Matthias Kaehlcke <mka@...omium.org>,
VinÃcius Tinti <viniciustinti@...il.com>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] scripts/package: snap-pkg target
On Fri, Dec 1, 2017 at 1:03 PM, Riku Voipio <riku.voipio@...aro.org> wrote:
>
> 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.
There's a lot more you can do inside a snapcraft.yaml (bundle external
files, override .config options, run pre or post scripts, etc) but by
embedding everything inside the kernel/kbuild plugins
you would loose all these options, and people would loose visibility
of these opportunities.
Besides, snapcraft requires a snapcraft.yaml by design, and i can't
remove that (such a change would never be accepted).
--
bye,
p.
Powered by blists - more mailing lists