[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAS0ieC+e0v+Gq-84_bJk-vZL2QHpRAjVePiPUEsVsJJ6g@mail.gmail.com>
Date: Wed, 20 Sep 2017 18:28:03 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Paolo Pisati <paolo.pisati@...onical.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
Hi Paolo,
2017-09-12 19:11 GMT+09:00 Paolo Pisati <paolo.pisati@...onical.com>:
> @@ -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?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists