Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Sean Whitton <spwhitton@spwhitton.name>
Newsgroups: linux.debian.maint.python
Subject: Re: git-dpm required?
Date: Thu, 02 Aug 2018 06:10:01 +0200
Message-ID: <wid61-2r1-1@gated-at.bofh.it>
References: <whruq-6Gi-3@gated-at.bofh.it> <whs77-6Tg-5@gated-at.bofh.it> <whtcS-7SM-5@gated-at.bofh.it> <whu8V-8sW-1@gated-at.bofh.it>
Old-Return-Path: <spwhitton@spwhitton.name>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 55
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10739

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hello,

On Tue 31 Jul 2018 at 12:00AM -0400, Sergio Durigan Junior wrote:

> On Monday, July 30 2018, Sean Whitton wrote:
>
>> Hello,
>>
>> On Mon 30 Jul 2018 at 09:54PM -0400, Sergio Durigan Junior wrote:
>>
>>> This is my understanding as well: git-dpm is not mandatory anymore, and
>>> gbp is the preferred tool.  I've been packaging all of my Python modules
>>> using gbp for a while.
>>
>> Do I have to use the full suite of gbp tools (e.g. gbp-pq) or is it
>> enough that `gbp buildpackage` will work?
>
> You don't have to use the full suite if you don't like.  The important
> thing is to have the repository in the correct format
> (debian/upstream/pristine-tar branches [or something else, as long as
> properly documented in d/gbp.conf], tags, etc.), so that other people
> can use gbp without problems.

Thank you.

Just to note that gbp will work with patches-applied too, but I won't do
that.

=2D-=20
Sean Whitton

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAltig/sACgkQaVt65L8G
YkBufBAAgkCBRzREUY0WL7wVBVEKvg5kb0YZUyHwJ7JHHMMqw95J6qJhQMj5KPLF
4IWvi/4SIQYeJI8deQ7xnnx/mPkULCbgI5YKyR9Cjuj++CcdyQT1cVNNfLXmhkfl
vQ60j5AiU88ZxMm9ZtKvmcj9GrIFNc6UzJ/BRj8yDArwNFjU3x3QAL6EhcgNgslR
j4mnTuac87e1UGpH8zziijOkc2ZSKOGiAZEv4cetc4Tyu5cpUharYaUttLwNkqFj
AsjKM6lbOktbkXFesEqbPp8m8h3X+0RZsOA7n/0AueM3FRZq8um1Q3yKbsZzLsYg
K3dowvUfYpU9SoDn5p4Uly4FDbdShpiTpRYGkI38XMB3aH+mf+YWyqADgLqZ0DUe
fb6ri6cZi1+BIDPrKRpoAchT0IBcQrDCKVE1eX5zECy3ZD4qCba6bgEJxe4zHyqc
HL+AS8FIqAu0t2Kv8q+IdFby9+axO5K4kE5+a9g47uTGRuJq311cboVV/O0fToNj
PZkeJNOIkKN5NJyf/u+GTIer0PHcea+Nw86wcD3VwIzom9tICk5ESOVRpoMBu45Y
BauKWT9rue8ROA/JhU3H45YB45uuvA3KxgJquDFZe6HzcFOEk2DD8Q6gCTf2l1Ic
X2CSBR3I6Lr6lwztkgoVd4too1HnZoLwiKtTh6VYwHDQAxk31nU=
=vnx5
-----END PGP SIGNATURE-----
--=-=-=--