Github messages for voidlinux
 help / color / mirror / Atom feed
From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: btop: Update to 1.3.2
Date: Thu, 15 Feb 2024 22:14:52 +0100	[thread overview]
Message-ID: <20240215211452.218F524A97@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48113@inbox.vuxu.org>

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

New comment by zen0bit on void-packages repository

https://github.com/void-linux/void-packages/pull/48113#issuecomment-1947235846

Comment:
But as I study btop instructions before. ROCm must be presented at build time. If isn't btop should be builded without ROCm support. So provide library for usuall btop shouldn't be enough. Must be builded again with ROCm, as far as I understand...

So only difference will be ROCM_devel in makedepends

repektive somethink like this?:

```
# Template file for 'btop-ROCm'
pkgname=btop-ROCm
version=1.3.2
revision=1
build_style=gnu-makefile
makedepends="ROCm-SMI-devel"
short_desc="Monitor of resources"
maintainer="RunningDroid <runningdroid@zoho.com>"
license="Apache-2.0"
homepage="https://github.com/aristocratos/btop"
changelog="https://raw.githubusercontent.com/aristocratos/btop/main/CHANGELOG.md"
distfiles="https://github.com/aristocratos/btop/archive/refs/tags/v${version}.tar.gz"
checksum=331d18488b1dc7f06cfa12cff909230816a24c57790ba3e8224b117e3f0ae03e
conflicts=btop
```

  parent reply	other threads:[~2024-02-15 21:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  0:05 [PR PATCH] btop: Update to 1.3.0 zen0bit
2024-01-08  0:46 ` Calandracas606
2024-01-08  0:48 ` Calandracas606
2024-01-10  2:41 ` [PR PATCH] [Updated] " zen0bit
2024-02-15 16:00 ` mdkcore0
2024-02-15 16:51 ` [PR PATCH] [Updated] " zen0bit
2024-02-15 17:57 ` btop: Update to 1.3.2 Calandracas606
2024-02-15 18:06 ` zen0bit
2024-02-15 18:13 ` Calandracas606
2024-02-15 18:14 ` zen0bit
2024-02-15 18:20 ` Calandracas606
2024-02-15 19:08 ` Calandracas606
2024-02-15 19:43 ` Calandracas606
2024-02-15 20:14 ` zen0bit
2024-02-15 20:15 ` zen0bit
2024-02-15 21:14 ` zen0bit [this message]
2024-02-15 21:21 ` cinerea0
2024-02-15 21:36 ` Calandracas606
2024-02-15 22:46 ` Calandracas606
2024-03-28  1:30 ` dm17
2024-03-28  1:30 ` dm17
2024-03-28  2:18 ` Calandracas606
2024-03-28 10:23 ` [PR PATCH] [Updated] " zen0bit

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=20240215211452.218F524A97@inbox.vuxu.org \
    --to=zen0bit@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).