New package: soju-0.3.0

[flupe]

General

• This is a new package and it conforms to the 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
• I generally don't use the affected packages but briefly tested this PR

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)

[Vaelatern]

srcpkgs/soju/template: Place distfiles= after changelog=
srcpkgs/soju/template:7: short_desc should not start with an article
srcpkgs/soju/template:20: please indent with tabs

[flupe]

Thanks, my bad I forgot to run xlint before submitting a PR.
I moved go and scdoc to makehostdepends, however it's unclear to me whether scdoc must be here or in makedepends.

[flupe]

Thanks for the review, I made the recommended changes. Uses the go build-style now.
Also removed the soju system user as it looked like more work than necessary.
I think I made the mistake of doing make doc/soju.1 rather than using scdoc in post_install(), but other than that I think it's done.

[Duncaen]

This should use a separate user, there is no reason to run an irc bouncer as root.

system_accounts="_soju"

and exec chpst -u _soju soju ... in the run file.

I also switched the log and database directories, not sure if this would make sense:

make_dirs="/var/db/soju/ 750 _soju _soju
  /var/log/soju/ 750 _soju _soju"

And then chaning the default configuration to use those instead of /var/lib/soju.

[flupe]

@Duncaen

This should use a separate user, there is no reason to run an irc bouncer as root.

I completely agree with this statement. My only gripe was that the database is only created when running sojuctl:

sojuctl -config /etc/soju/config create-user username -admin

And users would have to make sure it is ran as _soju so that the service can read it. Is there a way to document this?
Also, is there a naming convention for system users on void, why _soju rather than soju? (Ah, found it on the manual)

I also switched the log and database directories, not sure if this would make sense:

Yes, makes a lot of sense. On it.

[flupe]

Did all the recommended changes. Defining a _soju system user, providing an alternative default config using /var/log/soju and /var/db/soju.
Everything seems to work fine now.

Thank you all, sorry for the tedious process, it's my first template. Slowly getting used to the void process.

[Duncaen]

Some packages have a void specific readme, this would be a good case for that. This is done by adding a README.voidlinux into files and installing it with vdoc "${FILESDIR}/README.voidlinux".

[flupe]

Added a README.voidlinux.

[Duncaen]

Do you mind updating this to 0.3.0, this has been sitting a while and I don't see anything else blocking a merge.

[flupe]

Done!