Github messages for voidlinux
 help / color / mirror / Atom feed
From: michalszmidt <michalszmidt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: hctl-0.2.2
Date: Tue, 05 Sep 2023 21:09:44 +0200	[thread overview]
Message-ID: <20230905190944.Z_VC2G8tIG8et5mhD4caJ9LDWP6PUBgec-bWb_sv1c0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45905@inbox.vuxu.org>

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

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

https://github.com/michalszmidt/void-packages new_hctl
https://github.com/void-linux/void-packages/pull/45905

New package: hctl-0.2.2
**Question**
Do you need Cargo.lock, or this approach is acceptable?

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

_note:_
- `xlint` reports no problems
- tested with `XBPS_CHECK_PKGS=yes` and `-Q`

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**


<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-glibc
  - [x] armv7l-glibc
  - [x] armv6l-glibc
  - [x] i686-glibc

_note:_
- cross-compile for `ppc64-glibc` fails on make glibc, so probably native runner would succeed
- `riscv64` not tested
- not tested on void `*-musl` **but**, on alpine succeeds with `x86_64` and `aarch64`, see [here](https://cirrus-ci.com/build/6405859526311936)

_About:_
This tool allows to manage host domain blocking (hostlist generation from multiple sources, record de-duplication). It operates in parallel. Also it's optimized for memory. It's cool comparing to some nasty scripts or sed especially when you count records in millions.

_Info:_
- [Alpine Linux Package request](https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/51062) - uses musl, may be helpful for bug tracing

_Disclaimer:_
I'm a hctl author.

Have a nice day!

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

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

From 7b2f7a73c975a87a3df4dbd390b94db031a3a7b4 Mon Sep 17 00:00:00 2001
From: michalszmidt <michal.sz@disroot.org>
Date: Mon, 4 Sep 2023 13:56:40 +0000
Subject: [PATCH] New package: hctl-0.2.2

---
 srcpkgs/hctl/template | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 srcpkgs/hctl/template

diff --git a/srcpkgs/hctl/template b/srcpkgs/hctl/template
new file mode 100644
index 0000000000000..2d71bf6d4990b
--- /dev/null
+++ b/srcpkgs/hctl/template
@@ -0,0 +1,22 @@
+# Template file for 'hctl'
+pkgname=hctl
+version=0.2.2
+revision=1
+build_style=cargo
+hostmakedepends="pkg-config"
+makedepends="openssl-devel"
+depends="openssl"
+short_desc="CLI tool to merge hostlists for dns blocker like pihole"
+maintainer="Michał Szmidt <michal.sz@disroot.org>"
+license="BSD-3-Clause-No-Military-License"
+homepage="https://github.com/michalszmidt/hctl"
+distfiles="https://github.com/michalszmidt/hctl/archive/refs/tags/${version}.tar.gz"
+checksum=8b74e520a8412d39b1abe6ac944dc2e2c454c66affb227569f7d363f14deb5d3
+
+pre_build() {
+	cargo generate-lockfile
+}
+
+post_install() {
+	vlicense LICENSE
+}

  parent reply	other threads:[~2023-09-05 19:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 14:20 [PR PATCH] " michalszmidt
2023-09-05 17:51 ` classabbyamp
2023-09-05 18:36 ` michalszmidt
2023-09-05 18:48 ` [PR REVIEW] " classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 18:48 ` classabbyamp
2023-09-05 19:09 ` michalszmidt [this message]
2023-09-05 19:15 ` michalszmidt
2023-09-05 19:16 ` michalszmidt
2023-09-05 19:29 ` [PR REVIEW] " classabbyamp
2023-09-05 20:18 ` michalszmidt
2023-09-05 20:19 ` classabbyamp
2023-09-05 23:57 ` [PR PATCH] [Updated] " michalszmidt
2023-09-05 23:57 ` [PR REVIEW] " michalszmidt
2023-09-06  0:39 ` [PR PATCH] [Updated] New package: hctl-0.2.2.1 michalszmidt
2023-09-06  0:40 ` [PR REVIEW] " michalszmidt
2023-09-07 12:11 ` michalszmidt
2023-10-14 11:55 ` [PR PATCH] [Updated] " michalszmidt
2023-10-14 11:56 ` New package: hctl-0.2.4 michalszmidt
2023-10-14 12:00 ` [PR PATCH] [Updated] " michalszmidt
2023-12-06 13:47 ` michalszmidt
2023-12-06 14:39 ` michalszmidt
2023-12-06 14:40 ` michalszmidt
2024-02-13 16:21 ` New package: hctl-0.2.5 melroy89
2024-03-04 20:42 ` [PR PATCH] [Updated] " michalszmidt
2024-03-04 21:03 ` michalszmidt
2024-03-04 21:05 ` New package: hctl-0.2.6 michalszmidt

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=20230905190944.Z_VC2G8tIG8et5mhD4caJ9LDWP6PUBgec-bWb_sv1c0@z \
    --to=michalszmidt@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).