~alpine/aports

add dcc-servers.net dcc to testing, with sub packages for dccif and dccm v1 NEEDS REVISION

Duncan Bellamy: 1
 add dcc-servers.net dcc to testing, with sub packages for dccif and dccm

 1 files changed, 61 insertions(+), 0 deletions(-)
Hi Kevin,
Thanks for the feedback, I will edit and resubmit.

I submitted an rspamd patch as well to update to 2.2 and tried to amend the commit after I found some typos but it kept submitting the old patch with new subject.

Thanks,
Duncan
Export patchset (mbox)
How do I use this?

Copy & paste the following snippet into your terminal to import this patchset into git:

curl -s https://lists.alpinelinux.org/~alpine/aports/patches/3234/mbox | git am -3
Learn more about email & git

[PATCH] add dcc-servers.net dcc to testing, with sub packages for dccif and dccm Export this patch

---
 testing/dcc/APKBUILD | 61 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 61 insertions(+)
 create mode 100644 testing/dcc/APKBUILD

diff --git a/testing/dcc/APKBUILD b/testing/dcc/APKBUILD
new file mode 100644
index 0000000000..6efcfd6e3b
--- /dev/null
+++ b/testing/dcc/APKBUILD
@@ -0,0 +1,61 @@
# Contributor: Duncan Bellamy <dunk@denkimushi.com>
# Maintainer: Duncan Bellamy <dunk@denkimushi.com>
pkgname="dcc"
pkgver="2.3.167"
pkgrel=1
pkgdesc="Distributed Checksum Clearinghouses or DCC spam filter"
url="https://www.dcc-servers.net/dcc/"
arch="all"
license="Distributed Checksum Clearinghouse"
pkgusers="_dcc"
pkggroups="_dcc"
depends="wget"
makedepends="libmilter-dev"
subpackages="$pkgname-dccifd $pkgname-dccm $pkgname-doc"
source="https://www.dcc-servers.net/src/dcc/old/dcc-2.3.167.tar.Z"
options="!check"

prepare() {
		default_prepare
	sed -i 's+DCC_UNIX+DCC_UNIX\n#include <sys\/types.h>+g' "$srcdir"/$pkgname-$pkgver/include/dcc_types.h
}

unpack() {
	cd "$srcdir"
	tar -xzf dcc*.tar.Z
}

build() {
	./configure \
		--with-installroot="$pkgdir" \
		--bindir="/usr/bin" \
		--mandir="/usr/man" \
		--with-uid=_dcc
	make
}

package() {
	make install
	install -Dm644 "$builddir"/LICENSE \
		"$pkgdir"/usr/share/licenses/$pkgname/LICENSE

	chmod 755 "$pkgdir"/var/dcc/libexec/dccsight
	cd "$pkgdir"/usr/bin
	chmod 755 cdcc dccproc
}

dccifd() {
	depends="dcc"
	mkdir -p "$subpkgdir"/var/dcc/libexec
	cd "$pkgdir"/var/dcc/libexec
	mv dccifd start-dccifd "$subpkgdir"/var/dcc/libexec/
}

dccm() {
	depends="dcc"
	mkdir -p "$subpkgdir"/var/dcc/libexec
	cd "$pkgdir"/var/dcc/libexec
	mv dccm start-dccm "$subpkgdir"/var/dcc/libexec/
}

sha512sums="384a572e5b18bed6aed08dce6ebc468d5737b0cb4774fe502f527b101a38b4bec1fdd73384c6fb437c21ae46aa56ae04c5c459737cdda6ab3ce186ff4f77cf98  dcc-2.3.167.tar.Z"
-- 
2.24.1

Hello Duncan,

Welcome to the Alpine Linux community, and thank you for your
contribution. I have placed some feedback inline.

Besides that, aport uses a specific standard for commit messages:

1) A generally followed commit standard where you have a short commit
subject soft limitted to about 50 characters, followed by a blank line,
and then more details about the commit (focussing more on why than what.
See this [post][commit-message] for more information.
2) Commit messages for packages are prefixed with the repo and package
name like this: 'testing/dcc: '.

So the commit message for this patch would be:

```
testing/dcc: new aport
```

The fact that there are subpackages is not that interesting (most
packages will have subpackages).

I hope this is clear, otherwise, feel free to ask questions.

Kind regards, Kevin.

On Fri, Jan 24, 2020 at 09:46:54PM +0000, Duncan Bellamy wrote: