Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] vlicense hook
Date: Thu, 30 Apr 2020 19:59:07 +0200	[thread overview]
Message-ID: <20200430175907.NZ4cf8z9JOHK5vMHFDjH3D3uM0SaUfZv9BVhqlGI9_8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21272@inbox.vuxu.org>

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

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/21272#issuecomment-622010268

Comment:
> I'd rather the hook be used for simple cases, and vlicense whenever anything gets complicated.
> So is it too confusing to have two ways to do things?

Yes, I think having two ways is too complicated. There will be need to look for license files in two parts of template while reviewing.
People are used to call vlicense, so they will be calling it in new templates: should we accept this? Will existing vlicense calls stay? Hook seem to work with sedding, but is it simple case?

Below is hook mod that handle globs. It fails if no file is matched by glob.

``` bash
# This hook install $license_file

hook() {
	local pair file target found
	cd "$wrksrc" || return 0
	for pair in $license_file
	do
		file=${pair%:*}
		if [ "$file" = "$pair" ]; then
			for i in $file; do
				vlicense "$i"
				found=yes
			done
		else
			target=${pair#*:}
			vlicense "$file" "$target"
		fi
	done
}
```

  parent reply	other threads:[~2020-04-30 17:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 15:46 [PR PATCH] " sgn
2020-04-23 15:48 ` sgn
2020-04-23 16:17 ` pullmoll
2020-04-24  0:10 ` sgn
2020-04-24  1:34 ` ahesford
2020-04-24  1:38 ` ahesford
2020-04-24  3:05 ` Vaelatern
2020-04-24  9:53 ` leahneukirchen
2020-04-24 10:40 ` xtraeme
2020-04-24 10:47 ` leahneukirchen
2020-04-24 14:06 ` Vaelatern
2020-04-24 14:10 ` xtraeme
2020-04-24 14:18 ` Vaelatern
2020-04-24 14:21 ` ahesford
2020-04-24 16:40 ` Chocimier
2020-04-24 16:48 ` leahneukirchen
2020-04-24 17:59 ` sgn
2020-04-24 18:02 ` sgn
2020-04-24 18:02 ` ahesford
2020-04-24 18:06 ` ahesford
2020-04-24 18:17 ` Vaelatern
2020-04-24 18:23 ` ahesford
2020-04-24 19:02 ` Chocimier
2020-04-25  0:31 ` Chocimier
2020-04-26  1:17 ` sgn
2020-04-30  1:06 ` sgn
2020-04-30  3:38 ` ahesford
2020-04-30  4:59 ` Anachron
2020-04-30  8:08 ` sgn
2020-04-30  8:09 ` sgn
2020-04-30 11:21 ` travankor
2020-04-30 11:25 ` travankor
2020-04-30 11:37 ` ahesford
2020-04-30 11:44 ` ahesford
2020-04-30 11:44 ` ahesford
2020-04-30 11:46 ` travankor
2020-04-30 14:45 ` Vaelatern
2020-04-30 17:59 ` Chocimier [this message]
2020-04-30 18:02 ` Chocimier
2020-04-30 18:29 ` Chocimier
2020-04-30 18:37 ` Chocimier
2020-09-19  3:42 ` [PR PATCH] [Closed]: " sgn

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=20200430175907.NZ4cf8z9JOHK5vMHFDjH3D3uM0SaUfZv9BVhqlGI9_8@z \
    --to=chocimier@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).