From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-R/lifecycle/
Date: Fri, 8 May 2020 00:27:28 +0000 (UTC) [thread overview]
Message-ID: <1588897642.91df3709b3425eeab232a37eac8ac299b2c4e8ac.Alessandro-Barbieri@gentoo> (raw)
commit: 91df3709b3425eeab232a37eac8ac299b2c4e8ac
Author: Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Fri May 8 00:07:32 2020 +0000
Commit: Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Fri May 8 00:27:22 2020 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=91df3709
dev-R/lifecycle: new package
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>
dev-R/lifecycle/Manifest | 1 +
dev-R/lifecycle/lifecycle-0.2.0.ebuild | 23 +++++++++++++++++++++++
dev-R/lifecycle/metadata.xml | 33 +++++++++++++++++++++++++++++++++
3 files changed, 57 insertions(+)
diff --git a/dev-R/lifecycle/Manifest b/dev-R/lifecycle/Manifest
new file mode 100644
index 0000000..3e7e9a0
--- /dev/null
+++ b/dev-R/lifecycle/Manifest
@@ -0,0 +1 @@
+DIST lifecycle_0.2.0.tar.gz 164455 BLAKE2B 9b6899716625eee5e74200a84fec473b79d97c57bc17510259efd39e814b2ddbfd5bf92ce789b543bd42578e7496ce69d92d2386d10c61464d5af7fe2272a53f SHA512 f939b65a7eaaff543ffaf7284b07d551d2f851a1975a17116d7cdd3561dcf2e60d79561912f6e007a3d60c8a4e78727e74a96532f2555a5d6cc365a6f1e1dde5
diff --git a/dev-R/lifecycle/lifecycle-0.2.0.ebuild b/dev-R/lifecycle/lifecycle-0.2.0.ebuild
new file mode 100644
index 0000000..fc5b32f
--- /dev/null
+++ b/dev-R/lifecycle/lifecycle-0.2.0.ebuild
@@ -0,0 +1,23 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI="7"
+
+inherit R-packages-guru
+
+DESCRIPTION='Manage the Life Cycle of your Package Functions'
+HOMEPAGE="
+ https://lifecycle.r-lib.org
+ https://github.com/r-lib/lifecycle
+ https://cran.r-project.org/package=lifecycle
+"
+SRC_URI="http://cran.r-project.org/src/contrib/lifecycle_0.2.0.tar.gz"
+LICENSE='GPL-3'
+
+IUSE="${IUSE-}"
+DEPEND="
+ >=dev-lang/R-3.2
+ dev-R/glue
+ >=dev-R/rlang-0.4.0
+"
+RDEPEND="${DEPEND-}"
diff --git a/dev-R/lifecycle/metadata.xml b/dev-R/lifecycle/metadata.xml
new file mode 100644
index 0000000..617c5c7
--- /dev/null
+++ b/dev-R/lifecycle/metadata.xml
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+ <maintainer type="person">
+ <email>lssndrbarbieri@gmail.com</email>
+ <name>Alessandro Barbieri</name>
+ </maintainer>
+ <longdescription lang="en">
+ Manage the life cycle of your exported functions with shared conventions, documentation badges, and non-invasive deprecation warnings. The 'lifecycle' package defines four development stages (experimental, maturing, stable, and questioning) and three deprecation stages (soft-deprecated, deprecated, and defunct). It makes it easy to insert badges corresponding to these stages in your documentation. Usage of deprecated functions are signalled with increasing levels of non-invasive verbosity.
+ </longdescription>
+ <upstream>
+ <bugs-to>
+ https://github.com/r-lib/lifecycle/issues
+ </bugs-to>
+ <doc lang="en">
+ https://cran.r-project.org/web//packages/lifecycle/lifecycle.pdf
+ </doc>
+ <changelog>
+ https://cran.r-project.org/web//packages/lifecycle/news/news.html
+ </changelog>
+ <maintainer>
+ <name>
+ Lionel Henry
+ </name>
+ <email>
+ lionel@rstudio.com
+ </email>
+ </maintainer>
+ <remote-id type="github">
+ r-lib/lifecycle
+ </remote-id>
+ </upstream>
+</pkgmetadata>
next reply other threads:[~2020-05-08 0:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 0:27 Alessandro Barbieri [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-14 22:42 [gentoo-commits] repo/proj/guru:dev commit in: dev-R/lifecycle/ Alessandro Barbieri
2021-05-04 0:14 Alessandro Barbieri
2021-05-16 15:28 Alessandro Barbieri
2022-03-07 1:18 Alessandro Barbieri
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=1588897642.91df3709b3425eeab232a37eac8ac299b2c4e8ac.Alessandro-Barbieri@gentoo \
--to=lssndrbarbieri@gmail.com \
--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