From: Ralph Seichter <gentoo@seichter.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] New Python application with multiple new dependencies
Date: Sat, 13 Apr 2019 22:27:57 +0200 [thread overview]
Message-ID: <877ebx7ir6.fsf@ra.horus-it.com> (raw)
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?
1. Create one pull request that contains separate commits for adding
each of the four Python packages?
2. Create four separate pull requests?
3. Find out there is an eclass I have missed so far which performs the
equivalent of "pip install monty" and create an ebuild based on it?
4. None of the above.
-Ralph
next reply other threads:[~2019-04-13 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 20:27 Ralph Seichter [this message]
2019-04-13 21:03 ` [gentoo-dev] New Python application with multiple new dependencies Michał Górny
2019-04-13 23:05 ` Brian Dolbec
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=877ebx7ir6.fsf@ra.horus-it.com \
--to=gentoo@seichter.de \
--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