From: Barbarossa93 <Barbarossa93@users.noreply.github.com> To: ml@inbox.vuxu.org Subject: Re: [PR PATCH] [Updated] New package: xcolor-0.5.1 Date: Thu, 13 Jan 2022 00:44:05 +0100 [thread overview] Message-ID: <20220112234405.nyYLHjvIOoS-XE1fq8TvT8w3f8n0eC-61vUVKLBLVSw@z> (raw) In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33616@inbox.vuxu.org> [-- Attachment #1: Type: text/plain, Size: 1601 bytes --] There is an updated pull request by Barbarossa93 against master on the void-packages repository https://github.com/Barbarossa93/void-packages xcolor https://github.com/void-linux/void-packages/pull/33616 New package: xcolor-0.5.1 <!-- Mark items with [x] where applicable --> #### General - [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements) #### Have the results of the proposed changes been tested? - [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me - [ ] I generally don't use the affected packages but briefly tested this PR <!-- If GitHub CI cannot be used to validate the build result (for example, if the build is likely to take several hours), make sure to [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration). When skipping CI, uncomment and fill out the following section. Note: for builds that are likely to complete in less than 2 hours, it is not acceptable to skip CI. --> <!-- #### Does it build and run successfully? (Please choose at least one native build and, if supported, at least one cross build. More are better.) - [x] I built this PR locally for my native architecture, (ARCH-LIBC) - [ ] I built this PR locally for these architectures (if supported. mark crossbuilds): - [ ] aarch64-musl - [ ] armv7l - [ ] armv6l-musl --> A patch file from https://github.com/void-linux/void-packages/pull/33616.patch is attached [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: github-pr-xcolor-33616.patch --] [-- Type: text/x-diff, Size: 1046 bytes --] From b5276550f352dedd6d29935adec5d9531cff35ac Mon Sep 17 00:00:00 2001 From: Cullen Ross <cullenrss@gmail.com> Date: Wed, 12 Jan 2022 18:43:58 -0500 Subject: [PATCH] New package: xcolor-0.5.1_1 --- srcpkgs/xcolor/template | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 srcpkgs/xcolor/template diff --git a/srcpkgs/xcolor/template b/srcpkgs/xcolor/template new file mode 100644 index 000000000000..2c54b2a1d860 --- /dev/null +++ b/srcpkgs/xcolor/template @@ -0,0 +1,17 @@ +# Template file for 'xcolor' +pkgname=xcolor +version=0.5.1 +revision=1 +build_style=cargo +hostmakedepends="pkg-config python3" +makedepends="libX11-devel libXcursor-devel libXrender-devel" +short_desc="Lightweight color picker for X11" +maintainer="Cullen Ross <cullenrss@gmail.com>" +license="MIT" +homepage="https://github.com/Soft/xcolor" +distfiles="https://github.com/Soft/xcolor/archive/refs/tags/${version}.tar.gz" +checksum=cff417d0ccbece766c66a183413e167868fdbd98b8129516ff9021a4b11a5647 + +post_install() { + vlicense LICENSE +}
next prev parent reply other threads:[~2022-01-12 23:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-18 12:09 [PR PATCH] Add new xcolor 0.5.1 package Barbarossa93 2021-10-19 13:21 ` New package: xcolor-0.5.1 Barbarossa93 2021-10-29 2:03 ` abenson 2021-10-29 2:04 ` [PR REVIEW] " abenson 2021-11-02 7:16 ` biopsin 2021-11-22 11:18 ` [PR PATCH] [Updated] " Barbarossa93 2021-11-22 11:23 ` Barbarossa93 2021-11-22 12:13 ` Barbarossa93 2022-01-12 23:29 ` [PR PATCH] [Updated] " Barbarossa93 2022-01-12 23:38 ` Barbarossa93 2022-01-12 23:44 ` Barbarossa93 [this message] 2022-01-12 23:50 ` Barbarossa93 2022-01-21 10:08 ` wael444 2022-06-09 2:12 ` github-actions 2022-06-23 2:15 ` [PR PATCH] [Closed]: " github-actions 2022-06-23 21:56 ` classabbyamp
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=20220112234405.nyYLHjvIOoS-XE1fq8TvT8w3f8n0eC-61vUVKLBLVSw@z \ --to=barbarossa93@users.noreply.github.com \ --cc=ml@inbox.vuxu.org \ --subject='Re: [PR PATCH] [Updated] New package: xcolor-0.5.1' \ /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
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).