From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42542)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peterx@redhat.com>) id 1fTQ2P-0001vk-R4
	for qemu-devel@nongnu.org; Thu, 14 Jun 2018 07:03:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peterx@redhat.com>) id 1fTQ2K-0005aK-1o
	for qemu-devel@nongnu.org; Thu, 14 Jun 2018 07:03:33 -0400
Received: from mx3-rdu2.redhat.com ([66.187.233.73]:34588 helo=mx1.redhat.com)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <peterx@redhat.com>) id 1fTQ2J-0005a8-UB
	for qemu-devel@nongnu.org; Thu, 14 Jun 2018 07:03:27 -0400
Date: Thu, 14 Jun 2018 19:03:22 +0800
From: Peter Xu <peterx@redhat.com>
Message-ID: <20180614110322.GD14019@xz-mi>
References: <20180612062430.GA15344@xz-mi>
	<CAFEAcA_Bh4U1X_FDbakcc7YDBHFrkCjCKGrtuTWegn7rAGZUeQ@mail.gmail.com>
	<20180613040259.GI15344@xz-mi> <20180613092809.GF27901@redhat.com>
	<20180614025521.GR15344@xz-mi> <20180614081420.GG6355@redhat.com>
	<CAFEAcA-d8mVd2d7mAAVH6aWGHwyi=9yzKiwm2pX9unJ5OaACxg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAFEAcA-d8mVd2d7mAAVH6aWGHwyi=9yzKiwm2pX9unJ5OaACxg@mail.gmail.com>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Is there a way to package QEMU binaries?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= <berrange@redhat.com>, QEMU Devel Mailing List <qemu-devel@nongnu.org>

On Thu, Jun 14, 2018 at 11:50:23AM +0100, Peter Maydell wrote:
> On 14 June 2018 at 09:14, Daniel P. Berrang=C3=A9 <berrange@redhat.com>=
 wrote:
> > On Thu, Jun 14, 2018 at 10:55:21AM +0800, Peter Xu wrote:
> >> Then is there an easy way to port the specfile and tools to QEMU
> >> repository so that we can pack that even with a git tree?
>=20
> > Well if we want to have a RPM spec file for QEMU distributed with ups=
tream
> > QEMU, then I think it would be better todo what libvirt does[2], and =
simply
> > have the real Fedora  specfile kept in QEMU git [3].
>=20
> I would prefer not to. I think packaging is a job for downstream
> distributors, and having our own (probably under-maintained)
> version of the packaging infrastructure in upstream git just
> makes things awkward for downstream, and requires us to make
> choices about which distros we think "important" enough to
> provide packaging for...

AFAIU that's not a problem; we can just provide more ways to package
the system gradually, just like what Linux did:

Kernel packaging:
  rpm-pkg             - Build both source and binary RPM kernel packages
  binrpm-pkg          - Build only the binary kernel RPM package
  deb-pkg             - Build both source and binary deb kernel packages
  bindeb-pkg          - Build only the binary kernel deb package
  snap-pkg            - Build only the binary kernel snap package (will c=
onnect to external hosts)
  tar-pkg             - Build the kernel as an uncompressed tarball
  targz-pkg           - Build the kernel as a gzip compressed tarball
  tarbz2-pkg          - Build the kernel as a bzip2 compressed tarball
  tarxz-pkg           - Build the kernel as a xz compressed tarball

But it seems that this package thing is not really that welcomed (and
after all we have multiple specfiles here and there).  Then I think
I'll just live with it now.

Regards,

--=20
Peter Xu