Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package Template for when out of Beta - Zig - Ziglang
Date: Sun, 05 Jan 2020 15:19:24 +0100	[thread overview]
Message-ID: <20200105141924.i7_r8w4J_QOeX9Vjsd9-CtPxWRAyrvWip_93z8HN1DQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-475@inbox.vuxu.org>

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

Closed issue by Vaelatern on void-packages repository

https://github.com/void-linux/void-packages/issues/475

Description:
Recommendation: this not be turned into a PR until such a time as the third stage works. That is to say, when the language gets out of absolute Beta quality software.

Recommendation: a build_option of 'bootstrap' be used to trigger a cmake build, else just rely on a preexisting zig package and run stage two and three to do the build (that means building the zig compiler twice, really necessary? Or just a stage 2 compiler will be adequate, since that has the same effect?)

```
# Template file for 'zig'
pkgname=zig
version=0.2.0
revision=1
build_style=cmake
makedepends="llvm clang zlib-devel libxml2-devel ncurses-devel"
short_desc="Robust, optimal, and clear programming language"
maintainer="Toyam Cox <Vaelatern@voidlinux.eu>"
license="MIT"
homepage="https://ziglang.org/"
distfiles="https://github.com/ziglang/zig/archive/${version}.tar.gz"
checksum=09843a3748bf8a5f1742fe93dbf45699f92051ecf479b23272b067dfc3837cc7

post_install() {
        vlicense LICENSE
}

do_check() {
        bin/zig build --build-file ../build.zig test
}
```

           reply	other threads:[~2020-01-05 14:19 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-475@inbox.vuxu.org>]

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=20200105141924.i7_r8w4J_QOeX9Vjsd9-CtPxWRAyrvWip_93z8HN1DQ@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).