public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/certbot-dns-dnsimple/
Date: Tue, 04 Mar 2025 22:45:54 +0000 (UTC)	[thread overview]
Message-ID: <1741128309.63217c764b0eed56c5fc4c360cf9b8f8c9571daa.sam@gentoo> (raw)

commit:     63217c764b0eed56c5fc4c360cf9b8f8c9571daa
Author:     Thibaud CANALE <thican <AT> thican <DOT> net>
AuthorDate: Mon Mar  3 14:22:50 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Mar  4 22:45:09 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=63217c76

app-crypt/certbot-dns-dnsimple: provide transition package

The new merged app-crypt/certbot has blockers on all the old split
modules like certbot-nginx, which leads to poor UX when users who have
e.g. certbot-nginx in their world file now to try to upgrade.

Add a dummy set of ebuilds for the old split modules to depend on the
merged certbot with the right USE, which we can last-rite in a while.

Signed-off-by: Thibaud CANALE <thican <AT> thican.net>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../certbot-dns-dnsimple-3.2.0-r100.ebuild         | 30 ++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/app-crypt/certbot-dns-dnsimple/certbot-dns-dnsimple-3.2.0-r100.ebuild b/app-crypt/certbot-dns-dnsimple/certbot-dns-dnsimple-3.2.0-r100.ebuild
new file mode 100644
index 000000000000..f38b47a761ba
--- /dev/null
+++ b/app-crypt/certbot-dns-dnsimple/certbot-dns-dnsimple-3.2.0-r100.ebuild
@@ -0,0 +1,30 @@
+# Copyright 1999-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DESCRIPTION="DNSimple Authenticator plugin for Certbot (Let’s Encrypt Client)"
+HOMEPAGE="
+	https://github.com/certbot/certbot
+	https://pypi.org/project/certbot-dns-dnsimple/
+	https://certbot-dns-dnsimple.readthedocs.io/en/stable/
+	https://letsencrypt.org/
+"
+
+LICENSE="metapackage"
+SLOT="0"
+
+KEYWORDS="~amd64 ~x86"
+
+# Meta package for transition
+# No need to upgrade thanks to ">="
+RDEPEND="
+	>=app-crypt/certbot-${PV}-r100[certbot-dns-dnsimple]
+"
+
+pkg_postinst() {
+	elog "This is a meta-package to help in transition to single package "
+	elog "app-crypt/certbot."
+	elog "It is advice to simply deselect this package and to emerge "
+	elog "app-crypt/certbot[certbot-dns-dnsimple] for this module."
+}


             reply	other threads:[~2025-03-04 22:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 22:45 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-10  5:43 [gentoo-commits] repo/gentoo:master commit in: app-crypt/certbot-dns-dnsimple/ Joonas Niilola
2025-04-23 12:13 Sam James
2025-04-17 20:20 Jakov Smolić
2025-04-17 19:06 Arthur Zamarin
2025-04-17 14:38 Sam James
2025-03-11  9:31 Sam James
2024-07-12 19:26 Michał Górny
2024-07-12 19:26 Michał Górny
2024-07-12 19:26 Michał Górny
2024-04-14 15:19 Matthew Smith
2024-04-13 14:04 Michał Górny
2023-07-31 17:09 Matthew Smith
2023-07-31 17:09 Matthew Smith
2023-07-31 17:09 Matthew Smith
2023-03-01 11:40 Matthew Smith
2023-01-10 14:42 Michał Górny
2022-11-05 22:03 Matthew Smith

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=1741128309.63217c764b0eed56c5fc4c360cf9b8f8c9571daa.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.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