From: "Florian Schmaus" <flow@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-erlang/p1_utils/
Date: Fri, 18 Oct 2024 08:27:05 +0000 (UTC) [thread overview]
Message-ID: <1729239689.2186a6df8db24ce87a1614e70f9762ca046b4819.flow@gentoo> (raw)
commit: 2186a6df8db24ce87a1614e70f9762ca046b4819
Author: Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 18 08:14:57 2024 +0000
Commit: Florian Schmaus <flow <AT> gentoo <DOT> org>
CommitDate: Fri Oct 18 08:21:29 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2186a6df
dev-erlang/p1_utils: add 1.0.26-r1 using rebar eclass
The rebar3 eclass currently does not install header files, but p1_utils
installs the p1_queue.hrl header. Hence, switch to rebar eclass for now.
Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>
.../p1_utils/{p1_utils-1.0.26.ebuild => p1_utils-1.0.26-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-erlang/p1_utils/p1_utils-1.0.26.ebuild b/dev-erlang/p1_utils/p1_utils-1.0.26-r1.ebuild
similarity index 96%
rename from dev-erlang/p1_utils/p1_utils-1.0.26.ebuild
rename to dev-erlang/p1_utils/p1_utils-1.0.26-r1.ebuild
index 564606c4d984..e402963ce2d1 100644
--- a/dev-erlang/p1_utils/p1_utils-1.0.26.ebuild
+++ b/dev-erlang/p1_utils/p1_utils-1.0.26-r1.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit rebar3
+inherit rebar
DESCRIPTION="Erlang utility modules from ProcessOne"
HOMEPAGE="https://github.com/processone/p1_utils"
next reply other threads:[~2024-10-18 8:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 8:27 Florian Schmaus [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-14 17:45 [gentoo-commits] repo/gentoo:master commit in: dev-erlang/p1_utils/ Florian Schmaus
2024-06-10 20:05 Arthur Zamarin
2022-09-21 19:56 Florian Schmaus
2022-07-05 8:52 Agostino Sarubbo
2022-05-17 20:02 Florian Schmaus
2022-04-10 17:40 Florian Schmaus
2022-01-20 20:10 Florian Schmaus
2021-12-10 13:06 Florian Schmaus
2021-07-08 18:37 Florian Schmaus
2021-07-08 15:37 Florian Schmaus
2021-06-01 9:35 Sam James
2020-10-12 14:24 Hanno Böck
2020-10-12 14:18 Hanno Böck
2020-08-06 11:52 Agostino Sarubbo
2020-08-06 11:47 Agostino Sarubbo
2020-06-23 18:59 Hanno Böck
2020-03-09 9:51 Hanno Böck
2019-12-16 11:33 Hanno Böck
2019-12-07 13:47 Sergei Trofimovich
2019-11-17 4:16 Matt Turner
2019-11-03 8:20 Hanno Boeck
2019-08-31 13:57 Hanno Boeck
2019-06-05 21:52 Andreas Sturmlechner
2019-06-04 7:53 Tobias Klausmann
2019-05-23 12:47 Mikle Kolyada
2019-05-21 18:50 Sergei Trofimovich
2018-10-15 22:06 Amadeusz Piotr Żołnowski
2018-07-01 9:11 Sergei Trofimovich
2018-06-25 13:36 Tobias Klausmann
2018-06-17 10:21 Sergei Trofimovich
2018-05-27 15:33 Mikle Kolyada
2018-05-27 14:14 Thomas Deutschmann
2017-12-16 8:20 Tobias Klausmann
2017-11-18 19:43 Sergei Trofimovich
2017-10-23 19:51 Thomas Deutschmann
2017-05-27 20:55 Amadeusz Piotr Żołnowski
2017-03-29 21:45 Amadeusz Piotr Żołnowski
2016-12-30 23:37 Amadeusz Piotr Żołnowski
2016-12-21 12:22 Tobias Klausmann
2016-08-20 20:03 Anthony G. Basile
2016-08-20 3:11 Matthias Maier
2016-06-07 22:24 Amadeusz Piotr Żołnowski
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=1729239689.2186a6df8db24ce87a1614e70f9762ca046b4819.flow@gentoo \
--to=flow@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