From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-containers/devcontainer/
Date: Sat, 7 Oct 2023 14:57:46 +0000 (UTC) [thread overview]
Message-ID: <1696690660.9a043f36c0d7b707e9ae20d46214fca4b853073c.xgqt@gentoo> (raw)
commit: 9a043f36c0d7b707e9ae20d46214fca4b853073c
Author: Maciej Barć <xgqt <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 7 13:07:24 2023 +0000
Commit: Maciej Barć <xgqt <AT> gentoo <DOT> org>
CommitDate: Sat Oct 7 14:57:40 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a043f36
app-containers/devcontainer: new package; add 0.52.0
Signed-off-by: Maciej Barć <xgqt <AT> gentoo.org>
app-containers/devcontainer/Manifest | 1 +
.../devcontainer/devcontainer-0.52.0.ebuild | 46 ++++++++++++++++++++++
app-containers/devcontainer/metadata.xml | 21 ++++++++++
3 files changed, 68 insertions(+)
diff --git a/app-containers/devcontainer/Manifest b/app-containers/devcontainer/Manifest
new file mode 100644
index 000000000000..1fbeab3ea9cc
--- /dev/null
+++ b/app-containers/devcontainer/Manifest
@@ -0,0 +1 @@
+DIST devcontainer-0.52.0.tgz 614149 BLAKE2B 1e71d4772ec799cf8709d1d350cb8db0ea61dd2c7e96be4d35555675f9784bb1ff71ba95b6816fa9f8b6bd62c9a2b801871d51ab9fd8b564052c5939be603e2f SHA512 1790c6f2933c343b17a52d87a065e78c6e90b59249efb14c4601fc39de9a89aa6a93d100664ad3180a779c01fc181a31e59026af6bd646c214a616c61aed634c
diff --git a/app-containers/devcontainer/devcontainer-0.52.0.ebuild b/app-containers/devcontainer/devcontainer-0.52.0.ebuild
new file mode 100644
index 000000000000..399665b46cde
--- /dev/null
+++ b/app-containers/devcontainer/devcontainer-0.52.0.ebuild
@@ -0,0 +1,46 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DESCRIPTION="Reference implementation of the Development Containers specification"
+HOMEPAGE="https://containers.dev/
+ https://github.com/devcontainers/cli/"
+SRC_URI="https://registry.npmjs.org/@devcontainers/cli/-/cli-${PV}.tgz
+ -> ${P}.tgz"
+S="${WORKDIR}/package"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+RDEPEND="
+ net-libs/nodejs
+"
+BDEPEND="
+ >=net-libs/nodejs-16[npm]
+"
+
+DOCS=( CHANGELOG.md README.md )
+
+src_compile() {
+ # Skip, nothing to compile here.
+ :
+}
+
+src_install() {
+ local -a my_npm_opts=(
+ --audit false
+ --color false
+ --foreground-scripts
+ --global
+ --offline
+ --omit dev
+ --prefix "${ED}/usr"
+ --progress false
+ --verbose
+ )
+ npm "${my_npm_opts[@]}" install "${DISTDIR}/${P}.tgz" || die "npm install failed"
+
+ einstalldocs
+}
diff --git a/app-containers/devcontainer/metadata.xml b/app-containers/devcontainer/metadata.xml
new file mode 100644
index 000000000000..07653ea3406a
--- /dev/null
+++ b/app-containers/devcontainer/metadata.xml
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+
+<pkgmetadata>
+ <maintainer type="person">
+ <email>xgqt@gentoo.org</email>
+ <name>Maciej Barć</name>
+ </maintainer>
+ <longdescription>
+ A Development Container (or Dev Container for short) allows you to use a
+ container as a full-featured development environment. It can be used to run
+ an application, to separate tools, libraries, or runtimes needed for
+ working with a codebase, and to aid in continuous integration and testing.
+ Dev containers can be run locally or remotely, in a private or public
+ cloud, in a variety of supporting tools and editors.
+ </longdescription>
+ <upstream>
+ <bugs-to>https://github.com/devcontainers/cli/issues/</bugs-to>
+ <remote-id type="github">devcontainers/cli</remote-id>
+ </upstream>
+</pkgmetadata>
next reply other threads:[~2023-10-07 14:57 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 14:57 Maciej Barć [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-17 13:39 [gentoo-commits] repo/gentoo:master commit in: app-containers/devcontainer/ Maciej Barć
2023-11-15 19:27 Maciej Barć
2023-11-15 19:27 Maciej Barć
2023-11-23 15:12 Maciej Barć
2023-11-30 16:54 Maciej Barć
2023-11-30 16:54 Maciej Barć
2023-12-08 0:29 Maciej Barć
2023-12-08 0:29 Maciej Barć
2023-12-16 21:45 Maciej Barć
2023-12-16 21:45 Maciej Barć
2023-12-22 1:03 Maciej Barć
2023-12-22 5:07 Sam James
2024-01-18 9:43 Maciej Barć
2024-01-22 5:53 Sam James
2024-01-23 22:07 Maciej Barć
2024-01-23 22:07 Maciej Barć
2024-02-14 17:01 Maciej Barć
2024-02-19 22:06 Sam James
2024-02-27 23:21 Sam James
2024-03-04 21:58 Maciej Barć
2024-03-04 21:58 Maciej Barć
2024-03-04 21:58 Maciej Barć
2024-03-15 21:51 Sam James
2024-03-23 0:49 Maciej Barć
2024-03-23 0:49 Maciej Barć
2024-04-04 9:01 Jakov Smolić
2024-04-11 1:38 Maciej Barć
2024-04-22 23:01 Maciej Barć
2024-04-23 1:31 Sam James
2024-05-08 12:42 Maciej Barć
2024-05-08 12:42 Maciej Barć
2024-05-24 0:34 Sam James
2024-06-04 15:17 Maciej Barć
2024-06-04 15:17 Maciej Barć
2024-06-07 17:46 Arthur Zamarin
2024-06-15 22:23 Maciej Barć
2024-06-15 22:23 Maciej Barć
2024-06-27 22:42 Maciej Barć
2024-07-09 2:56 Sam James
2024-07-12 12:35 Maciej Barć
2024-07-12 12:35 Maciej Barć
2024-07-21 19:48 Arthur Zamarin
2024-07-31 0:03 Maciej Barć
2024-07-31 0:03 Maciej Barć
2024-08-01 16:47 Arthur Zamarin
2024-08-17 13:27 Maciej Barć
2024-08-17 13:27 Maciej Barć
2024-08-17 15:33 Jakov Smolić
2024-09-03 18:32 Jakov Smolić
2024-09-03 18:44 Maciej Barć
2024-09-03 18:44 Maciej Barć
2024-09-06 23:11 Maciej Barć
2024-09-06 23:11 Maciej Barć
2024-09-11 23:30 Maciej Barć
2024-09-27 5:30 Arthur Zamarin
2024-10-12 14:45 Michał Górny
2024-10-30 15:18 Sam James
2024-11-04 0:19 Maciej Barć
2024-11-04 0:19 Maciej Barć
2024-11-04 0:19 Maciej Barć
2024-11-04 0:19 Maciej Barć
2024-11-04 0:19 Maciej Barć
2024-12-06 7:49 Sam James
2024-12-06 8:31 Maciej Barć
2025-02-04 12:52 Maciej Barć
2025-02-25 23:12 Maciej Barć
2025-03-15 19:55 Maciej Barć
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=1696690660.9a043f36c0d7b707e9ae20d46214fca4b853073c.xgqt@gentoo \
--to=xgqt@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