From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-86961-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 0C041138334
	for <garchives@archives.gentoo.org>; Sat, 13 Apr 2019 23:05:58 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 3BD98E0A93;
	Sat, 13 Apr 2019 23:05:55 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id E5FABE0A6D
	for <gentoo-dev@lists.gentoo.org>; Sat, 13 Apr 2019 23:05:54 +0000 (UTC)
Received: from professor-x (d108-172-195-239.bchsia.telus.net [108.172.195.239])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: dolsen)
	by smtp.gentoo.org (Postfix) with ESMTPSA id AE119340F78
	for <gentoo-dev@lists.gentoo.org>; Sat, 13 Apr 2019 23:05:53 +0000 (UTC)
Date: Sat, 13 Apr 2019 16:05:59 -0700
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Python application with multiple new
 dependencies
Message-ID: <20190413160559.6564b758@professor-x>
In-Reply-To: <f59ae1e74b180438ee8345ca543b7edf97e524fe.camel@gentoo.org>
References: <877ebx7ir6.fsf@ra.horus-it.com>
	<f59ae1e74b180438ee8345ca543b7edf97e524fe.camel@gentoo.org>
X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: cabffcf7-9714-4373-9fa2-cf0e733f674d
X-Archives-Hash: 04d3f3f69971f7604a260199a45a7a65

On Sat, 13 Apr 2019 23:03:53 +0200
Micha=C5=82 G=C3=B3rny <mgorny@gentoo.org> wrote:

> On Sat, 2019-04-13 at 22:27 +0200, Ralph Seichter wrote:
> > Hi folks,
> >=20
> > imagine a Python application "monty" with the following requirements
> > listed in setup.py:
> >=20
> >   install_requires=3D[ =20
> >     'ham>=3D1.0',
> >     'spam>=3D2.0',
> >     'eggs>=3D1.5' =20
> >   ]
> >=20
> > If I want to add "monty" as a new Gentoo package, and if none of
> > "ham", "spam" and "eggs" are so far available as Gentoo packages,
> > what is the recommended way of handling this situation? =20
>=20
> I presume you want to proxy-maintain all of those packages.
>=20
> >=20
> > 1. Create one pull request that contains separate commits for adding
> > each of the four Python packages? =20
>=20
> This one.  We generally find it easier when we see the big picture
> in one place.
>=20
> By the way, there's gentoo-proxy-maint@ ml for this kind of questions.
>=20


Also, it is best to state that these new pkgs are a depencency of
"monty" in their commit messages.  It can be clearer as to why these
are in the tree if "monty" drops them as a dependency later and there
are no other reverse deps for them in the tree.

ie: app-foo/ham: New pkg, depencency of app-foo/monty-1.2.3