From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Python application with multiple new dependencies
Date: Sat, 13 Apr 2019 16:05:59 -0700 [thread overview]
Message-ID: <20190413160559.6564b758@professor-x> (raw)
In-Reply-To: <f59ae1e74b180438ee8345ca543b7edf97e524fe.camel@gentoo.org>
On Sat, 13 Apr 2019 23:03:53 +0200
Michał Górny <mgorny@gentoo.org> wrote:
> On Sat, 2019-04-13 at 22:27 +0200, Ralph Seichter wrote:
> > Hi folks,
> >
> > imagine a Python application "monty" with the following requirements
> > listed in setup.py:
> >
> > install_requires=[
> > 'ham>=1.0',
> > 'spam>=2.0',
> > 'eggs>=1.5'
> > ]
> >
> > 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?
>
> I presume you want to proxy-maintain all of those packages.
>
> >
> > 1. Create one pull request that contains separate commits for adding
> > each of the four Python packages?
>
> This one. We generally find it easier when we see the big picture
> in one place.
>
> By the way, there's gentoo-proxy-maint@ ml for this kind of questions.
>
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
next prev parent reply other threads:[~2019-04-13 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 20:27 [gentoo-dev] New Python application with multiple new dependencies Ralph Seichter
2019-04-13 21:03 ` Michał Górny
2019-04-13 23:05 ` Brian Dolbec [this message]
2019-04-14 12:44 ` Ralph Seichter
2019-04-14 20:58 ` Mike Gilbert
2019-04-14 22:05 ` Ralph Seichter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190413160559.6564b758@professor-x \
--to=dolsen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox