1.6.4 has an additional contrib file

Unconditionally include manpage

Unmute install steps. Don't include gitignore.

No PORTREVISION, GH_TAGNAME
Add DISTVERSIONPREFIX

In D446#7, @swills wrote:

Any update?

svn doesn't seem to like to diff against a copied deleted file:

This is a svn cp of sysutils/backuppc-devel without maintainer submission.

Actually add DOCS option

Cover manpage in %%PORTDOCS%%
Update diff against a new commit: http://svnweb.freebsd.org/ports?view=revision&revision=361978

I overwrote a previous change -.-

In D189#23, @swills wrote:

I hesitate to mention it, but we're trying to avoid muting install commands, so all the @ under do-install probably should be removed. Go ahead and do that (don't bother asking submitter) and submit a new rev and I think that should take care of it.

Unsilence do-install steps

Minor updates for DOCS and lint

Maintainer submitted a new patch with some of our suggestions.

In D189#8, @swills wrote:

In D189#6, @milki wrote:

I'll ask again. I think this is fine if its the normal backuppc upgrade procedure and that it understands local configurations. My suspicion is that it essentially fixes syntax for the next version and adds new defaults.

So it's not really a config file?

That makes sense. If the local file has been modified since install, will it be properly overwritten by the port on upgrade/reinstall or would it be considered a dirty file and left untouched.

If the file has been modified, it won't be overwritten.

Use %%PORTDOCS%% and %%PORTEXAMPLES%% in plist

In D189#5, @swills wrote:

Also, I think that with staging the logic to install the config file in the Makefile isn't needed because the @exec stuff from plist gets run at install time.

In D189#10, @swills wrote:

I tested this with my on devel/gitolite port. I deleted content from a file that was listed in pkg-plist after installing the port; and on deinstall/install, re-install (upgrade), it seems to restore the file properly. This would contradict your statement -.-

Hmm, was this using @sample? Perhaps I'm confused.

In D189#8, @swills wrote:

In D189#6, @milki wrote:

That makes sense. If the local file has been modified since install, will it be properly overwritten by the port on upgrade/reinstall or would it be considered a dirty file and left untouched.

If the file has been modified, it won't be overwritten.

In D189#5, @swills wrote:

Strange. So the config file isn't specific to the user? If so, then fine, overwrite it. But if the config file is specific to the user, then we shouldn't overwrite it, we should leave it and give a pkg-message to update it.

Clean pkg-plist for stage-qa

In D189#3, @swills wrote:

I think the logic for the config file may be missing an "!", but it might be better to just use "@sample" if you can.