public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/toxic/
Date: Wed, 16 Dec 2020 08:29:26 +0000 (UTC)	[thread overview]
Message-ID: <1608107356.f1d94f6e979bcbde9f270d0a0f3ec545f294ea39.juippis@gentoo> (raw)

commit:     f1d94f6e979bcbde9f270d0a0f3ec545f294ea39
Author:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 16 08:09:06 2020 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Wed Dec 16 08:29:16 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f1d94f6e

net-im/toxic: DEPEND list indentations, cleaning in 0.10.0

Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 net-im/toxic/toxic-0.10.0.ebuild | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/net-im/toxic/toxic-0.10.0.ebuild b/net-im/toxic/toxic-0.10.0.ebuild
index 7936c90bcd7..eec33667d60 100644
--- a/net-im/toxic/toxic-0.10.0.ebuild
+++ b/net-im/toxic/toxic-0.10.0.ebuild
@@ -23,17 +23,25 @@ BDEPEND="dev-libs/libconfig"
 RDEPEND="net-libs/tox
 	net-misc/curl
 	sys-libs/ncurses:*
-	audio-notify? ( media-libs/freealut
-			media-libs/openal )
+	audio-notify? (
+		media-libs/freealut
+		media-libs/openal
+	)
 	notification? ( x11-libs/libnotify )
 	debug? ( llvm? ( sys-devel/llvm:* ) )
 	python? ( ${PYTHON_DEPS} )
-	qrcode? ( media-gfx/qrencode
-		png? ( media-libs/libpng ) )
-	sound? ( media-libs/openal
-		net-libs/tox[av] )
-	X? ( x11-base/xorg-proto
-		x11-libs/libX11 )"
+	qrcode? (
+		media-gfx/qrencode
+		png? ( media-libs/libpng )
+	)
+	sound? (
+		media-libs/openal
+		net-libs/tox[av]
+	)
+	X? (
+		x11-base/xorg-proto
+		x11-libs/libX11
+	)"
 
 DEPEND="${RDEPEND}"
 


             reply	other threads:[~2020-12-16  8:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16  8:29 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-25 20:47 [gentoo-commits] repo/gentoo:master commit in: net-im/toxic/ Jimi Huotari
2025-01-25 20:47 Jimi Huotari
2024-11-22 15:43 Joonas Niilola
2024-11-21  6:45 Sam James
2024-07-30 19:09 Pacho Ramos
2024-07-30 19:09 Pacho Ramos
2024-07-30 19:09 Pacho Ramos
2024-07-30 19:09 Pacho Ramos
2023-12-18  7:13 Joonas Niilola
2023-12-18  4:51 Sam James
2023-04-10  8:10 Joonas Niilola
2023-04-10  8:10 Joonas Niilola
2021-12-10 22:17 Jakov Smolić
2021-12-10 16:26 Jakov Smolić
2021-08-24  8:50 Joonas Niilola
2021-08-24  8:50 Joonas Niilola
2021-06-10  8:13 Joonas Niilola
2021-01-02  0:49 Sam James
2021-01-02  0:49 Sam James
2020-12-16  8:29 Joonas Niilola
2020-12-16  8:29 Joonas Niilola
2020-09-04 20:53 Sam James
2020-07-17 15:17 Agostino Sarubbo
2020-07-17 15:05 Agostino Sarubbo
2020-06-08  7:46 Joonas Niilola
2020-06-08  7:46 Joonas Niilola
2018-12-09  8:43 Michał Górny
2018-11-12 23:00 Andreas Sturmlechner
2018-08-12 16:58 Michał Górny
2017-12-13  9:03 Michael Palimaka
2017-12-12 21:46 Daniel Campbell
2017-09-28 22:11 Daniel Campbell
2017-08-30 17:19 Daniel Campbell
2017-02-24  1:06 Daniel Campbell
2017-02-22  9:21 Daniel Campbell
2016-12-19 20:17 Michał Górny
2016-10-28  8:00 Daniel Campbell

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=1608107356.f1d94f6e979bcbde9f270d0a0f3ec545f294ea39.juippis@gentoo \
    --to=juippis@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