Github messages for voidlinux
 help / color / mirror / Atom feed
From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: bazel-4.1.0
Date: Thu, 10 Jun 2021 09:41:25 +0200	[thread overview]
Message-ID: <20210610074125.J1hgvM4c8A2G1RmADAXYf_v8Op5UcXfnDtjnN3WzPj4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31382@inbox.vuxu.org>

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

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/pull/31382#issuecomment-858391644

Comment:
I have attempted this in the past. Your bazel template looks sane.

Bazel is not sane. Neither is anki, has a stupid mix of nodejs, bazel, python and rust.

Here's my template thus far, not for the latest version yet:
```
# Template file for 'anki'
pkgname=anki
version=2.1.42
revision=1
hostmakedepends="bazel python3-pip git protobuf rust cargo rsync"
makedepends="protobuf-devel glib-devel python3-PyQt5-webengine"
depends="python3-PyQt5-webengine python3-requests python3-SQLAlchemy
 python3-PyAudio python3-mpv python3-Markdown python3-send2trash
 python3-BeautifulSoup4 python3-decorator python3-jsonschema
 python3-protobuf python3-Flask-Cors python3-waitress"
short_desc="Spaced repetition flashcard program"
maintainer="fosslinux <fosslinux@aussies.space>"
license="AGPL-3.0-or-later"
homepage="https://apps.ankiweb.net"
changelog="https://apps.ankiweb.net/docs/changes.html"
distfiles="https://github.com/ankitects/anki/archive/${version}.tar.gz"
checksum=a23e1ad9cc9d2ec2031810c847ae15efcd315123c7e0c3b3def40bd6d451d9c9
python_version=3
patch_args="-Np1"

do_build() {
        # Bazel dies on ccache
        if [ "$CROSS_BUILD" ]; then
                export CC="$(command -v ${XBPS_CROSS_TRIPLET}-gcc)"
        else
                export CC="$(command -v gcc)"
        fi
        export PYTHON_SITE_PACKAGES="${XBPS_CROSS_BASE}/${py3_sitelib}"

        bazel build -c opt dist --jobs=1
        bsdtar -xf bazel-bin/dist.tar
}

do_install() {
        # I dislike bazel
        PIP_CONFIG_FILE=/dev/null TMPDIR=/tmp python3 -m pip install --isolated --root=${DESTDIR} --prefix=/usr --ignore-installed --no-deps bazel-dist/*.whl

        vbin qt/runanki.py anki
        vinstall qt/linux/anki.desktop 644 usr/share/applications
        vinstall qt/linux/anki.png 644 usr/share/pixmaps
        vinstall qt/linux/anki.xpm 644 usr/share/pixmaps
        vman qt/linux/anki.1

        vlicense LICENSE
}
```

Haven't worked on it for a while.

  parent reply	other threads:[~2021-06-10  7:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 22:13 [PR PATCH] " Filius-Patris
2021-06-10  0:40 ` [PR REVIEW] " ericonr
2021-06-10  0:40 ` ericonr
2021-06-10  7:02 ` [PR PATCH] [Updated] [WIP] " Filius-Patris
2021-06-10  7:41 ` fosslinux [this message]
2021-06-10  7:42 ` fosslinux
2021-06-10 21:29 ` [PR PATCH] [Updated] " Filius-Patris
2021-06-11  9:22 ` Filius-Patris
2021-06-11 15:39 ` [PR PATCH] [Updated] " Filius-Patris
2021-06-11 15:39 ` Filius-Patris
2021-06-11 15:56 ` Filius-Patris
2022-01-06 21:47 ` TobTobXX
2022-05-21  2:00 ` github-actions
2022-06-04  2:09 ` [PR PATCH] [Closed]: " github-actions
2023-11-23 12:02 ` Luciogi

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=20210610074125.J1hgvM4c8A2G1RmADAXYf_v8Op5UcXfnDtjnN3WzPj4@z \
    --to=fosslinux@users.noreply.github.com \
    --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).