Github messages for voidlinux
 help / color / mirror / Atom feed
From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: php-codesniffer-3.5.8
Date: Wed, 03 Mar 2021 20:36:37 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29212@inbox.vuxu.org> (raw)

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

There is a new pull request by reback00 against master on the void-packages repository

https://github.com/reback00/void-packages phpcs-branch
https://github.com/void-linux/void-packages/pull/29212

New package: php-codesniffer-3.5.8
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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.)
- [ ] 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/29212.patch is attached

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

From f8d998020c80c365814cdd91207a9fa585799dda Mon Sep 17 00:00:00 2001
From: reback00 <reback00@protonmail.com>
Date: Thu, 4 Mar 2021 01:30:28 +0600
Subject: [PATCH] New package: php-codesniffer-3.5.8

---
 srcpkgs/php-codesniffer/template | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 srcpkgs/php-codesniffer/template

diff --git a/srcpkgs/php-codesniffer/template b/srcpkgs/php-codesniffer/template
new file mode 100644
index 00000000000..c0bdbae8e3e
--- /dev/null
+++ b/srcpkgs/php-codesniffer/template
@@ -0,0 +1,24 @@
+# Template file for 'php-codesniffer'
+pkgname=php-codesniffer
+_pkgname=PHP_CodeSniffer
+version=3.5.8
+revision=1
+build_style=fetch
+depends="php"
+short_desc="Tokenizes PHP files and detects violations of coding standards"
+maintainer="reback00 <reback00@protonmail.com>"
+license="BSD-3-Clause"
+homepage="https://github.com/squizlabs/PHP_CodeSniffer"
+distfiles="https://github.com/squizlabs/${_pkgname}/releases/download/${version}/phpcs.phar
+ https://github.com/squizlabs/${_pkgname}/releases/download/${version}/phpcbf.phar
+ https://raw.githubusercontent.com/squizlabs/${_pkgname}/${version}/licence.txt"
+checksum="6a2ae49e677d471dbeb8a8bcf67f714611250024c15d538a543db5b7ae6df50c
+ 6079de7bb0fcafe020d5a5dc44dfe88a8ff57b253a4dfd2bfde90ebe3d189195
+ 821c1697ab88bb71a5d1637743024e455d87074b8a5d0732f85205bd40cba6c9"
+
+do_install() {
+	vbin phpcs.phar phpcs
+	vbin phpcbf.phar phpcbf
+
+	vlicense licence.txt
+}

             reply	other threads:[~2021-03-03 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 19:36 reback00 [this message]
2021-03-11 21:17 ` [PR PATCH] [Updated] " reback00
2021-03-11 21:20 ` reback00
2022-05-06  2:08 ` github-actions
2022-05-20  2:11 ` [PR PATCH] [Closed]: " github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29212@inbox.vuxu.org \
    --to=reback00@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).