From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: 72594@debbugs.gnu.org
Cc: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
Subject: [bug#72594] [PATCH 1/7] gnu: Add go-github-com-gofrs-flock.
Date: Mon, 12 Aug 2024 20:26:23 +0300 [thread overview]
Message-ID: <4a9952c6c7486f38bd83fe9962ce43fa35699f5e.1723483365.git.poptsov.artyom@gmail.com> (raw)
In-Reply-To: <cover.1723483365.git.poptsov.artyom@gmail.com>
* gnu/packages/golang.scm (go-github-com-gofrs-flock): New variable.
Change-Id: If6856319258ec93f4119f4f7ec79d206d7e1087d
---
gnu/packages/golang.scm | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/gnu/packages/golang.scm b/gnu/packages/golang.scm
index 799a7d75ce..e74c50f2e7 100644
--- a/gnu/packages/golang.scm
+++ b/gnu/packages/golang.scm
@@ -2556,6 +2556,33 @@ (define-public go-github-com-gizak-termui
mouse, and terminal resizing events.")
(license license:expat)))
+(define-public go-github-com-gofrs-flock
+ (package
+ (name "go-github-com-gofrs-flock")
+ (version "0.12.1")
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/gofrs/flock/")
+ (commit (string-append "v" version))))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32 "0kfnbcahr9x61k40wsrqzxxr3ybix0jqsm4ibpjgnhfgrln7ag8v"))))
+ (build-system go-build-system)
+ (arguments
+ '(#:import-path "github.com/gofrs/flock"))
+ (native-inputs (list go-github-com-stretchr-testify))
+ (propagated-inputs (list go-golang-org-x-sys))
+ (home-page "https://github.com/gofrs/flock/")
+ (synopsis "Thread-safe file locking library in Go")
+ (description
+ "@code{flock} implements a thread-safe file lock.
+
+It also includes a non-blocking @code{TryLock} function to allow locking without
+blocking execution.")
+ (license license:bsd-3)))
+
(define-public go-github-com-golangplus-fmt
(package
(name "go-github-com-golangplus-fmt")
--
2.45.2
next prev parent reply other threads:[~2024-08-12 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 17:24 [bug#72594] [PATCH 0/7] Add some of the Google gvisor dependencies Artyom V. Poptsov
2024-08-12 17:26 ` Artyom V. Poptsov [this message]
2024-08-12 17:26 ` [bug#72594] [PATCH 2/7] gnu: Add go-github-com-google-subcommands Artyom V. Poptsov
2024-08-12 17:26 ` [bug#72594] [PATCH 3/7] gnu: Add go-github-com-mattbaird-jsonpatch Artyom V. Poptsov
2024-08-12 17:26 ` [bug#72594] [PATCH 4/7] gnu: Add go-github-com-mohae-deepcopy Artyom V. Poptsov
2024-08-12 17:26 ` [bug#72594] [PATCH 5/7] gnu: Add go-github-com-containerd-fifo Artyom V. Poptsov
2024-08-12 17:26 ` [bug#72594] [PATCH 6/7] gnu: Add go-github-com-containerd-typeurl Artyom V. Poptsov
2024-08-12 17:26 ` [bug#72594] [PATCH 7/7] gnu: Add go-github-com-containerd-typeurl-v2 Artyom V. Poptsov
2024-08-21 13:57 ` bug#72594: [PATCH 0/7] Add some of the Google gvisor dependencies Sharlatan Hellseher
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a9952c6c7486f38bd83fe9962ce43fa35699f5e.1723483365.git.poptsov.artyom@gmail.com \
--to=poptsov.artyom@gmail.com \
--cc=72594@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).