Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: otus-2.0
Date: Fri, 12 Jul 2019 13:44:35 +0200	[thread overview]
Message-ID: <20190712114435.I5BZX_DKw6pAOfgZFbBhlWkq7SCi0iY4vysLPVAHXDA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13026@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

There is an updated pull request by rc-05 against master on the void-packages repository

https://github.com/rc-05/void-packages personal
https://github.com/void-linux/void-packages/pull/13026

New package: otus-2.0


A patch file from https://github.com/void-linux/void-packages/pull/13026.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-personal-13026.patch --]
[-- Type: application/text/x-diff, Size: 1106 bytes --]

From 583d9a5d4ba200470dfda059cbadc524b17b7de0 Mon Sep 17 00:00:00 2001
From: rc-05 <rc23@email.it>
Date: Thu, 13 Jun 2019 00:00:40 +0200
Subject: [PATCH] New package: otus-2.0

Added "nocross" flag.

The repl for the otus interpreter could not be compiled for architectures other that i686 and amd64
---
 srcpkgs/otus/template | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 srcpkgs/otus/template

diff --git a/srcpkgs/otus/template b/srcpkgs/otus/template
new file mode 100644
index 00000000000..dac316ca31f
--- /dev/null
+++ b/srcpkgs/otus/template
@@ -0,0 +1,18 @@
+# Template file for 'otus'
+pkgname=otus
+version=2.0
+revision=1
+wrksrc=ol-${version}
+build_style=gnu-makefile
+short_desc="Purely functional dialect of Lisp"
+maintainer="rc-05 <rc23@email.it>"
+license="LGPL-3.0-or-later, MIT"
+homepage="https://yuriy-chumak.github.io/ol/"
+distfiles="https://github.com/yuriy-chumak/ol/archive/v${version}.tar.gz"
+checksum=5ad537b6bd032549334d1c72e742b78b7d40ccb8d1491d5cf0ce952964deeeea
+nocross="Failed to compile repl"
+
+post_install() {
+	vlicense LICENSE
+}
+

  parent reply	other threads:[~2019-07-12 11:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 10:14 [PR PATCH] " voidlinux-github
2019-07-12 10:16 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-12 10:16 ` voidlinux-github
2019-07-12 10:29 ` voidlinux-github
2019-07-12 10:29 ` voidlinux-github
2019-07-12 11:12 ` voidlinux-github
2019-07-12 11:12 ` voidlinux-github
2019-07-12 11:32 ` voidlinux-github
2019-07-12 11:32 ` voidlinux-github
2019-07-12 11:37 ` voidlinux-github
2019-07-12 11:37 ` voidlinux-github
2019-07-12 11:44 ` voidlinux-github [this message]
2019-07-12 11:44 ` voidlinux-github
2019-07-13  9:17 ` voidlinux-github
2019-07-13 10:54 ` voidlinux-github
2019-07-13 10:59 ` voidlinux-github
2019-07-13 11:12 ` voidlinux-github
2019-07-13 11:12 ` voidlinux-github
2019-07-13 11:14 ` voidlinux-github
2019-07-13 11:15 ` voidlinux-github
2019-07-13 11:59 ` [PR PATCH] [Closed]: " voidlinux-github
2019-07-13 11:59 ` voidlinux-github

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=20190712114435.I5BZX_DKw6pAOfgZFbBhlWkq7SCi0iY4vysLPVAHXDA@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).