[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMsH0TT2nPnT885GqcrK2aoHtXTBqCmDSkL=ZLkfumzonFCbJA@mail.gmail.com>
Date: Mon, 27 Nov 2017 11:46:09 +0100
From: Paolo Pisati <paolo.pisati@...onical.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Michal Marek <mmarek@...e.com>,
VinÃcius Tinti <viniciustinti@...il.com>,
Behan Webster <behanw@...verseincode.com>,
Matthias Kaehlcke <mka@...omium.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] scripts/package: snap-pkg target
On Wed, Sep 20, 2017 at 11:28 AM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
>> @@ -0,0 +1,14 @@
>> +name: kernel
>> +version: KERNELRELEASE
>> +summary: Linux kernel
>> +description: The upstream Linux kernel
>> +grade: stable
>> +confinement: strict
>> +type: kernel
>> +
>> +parts:
>> + kernel:
>> + plugin: kernel
>> + source: SRCTREE
>> + source-type: git
>> + kconfigfile: SRCTREE/.config
>
>
> Other targets such as rpm-pkg and deb-pkg
> work without relying on git.
>
> However, snap-pkg every time does "git clone", so
> changes added to the source tree, but not committed yet,
> are not reflected to the package.
>
> Is it possible to work with a tarball,
> like other targets do?
Thanks for your feedback Yamada-san.
Yes, switching to a tarball is doable and i'll send a v3 with that change.
--
bye,
p.
Powered by blists - more mailing lists