ports/64425: [NEW PORT]: net/netatalk-devel
Oliver Eikemeier
eikemeier at fillmore-labs.com
Fri Mar 19 13:10:19 UTC 2004
The following reply was made to PR ports/64425; it has been noted by GNATS.
From: Oliver Eikemeier <eikemeier at fillmore-labs.com>
To: tom at replic8.net
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: ports/64425: [NEW PORT]: net/netatalk-devel
Date: Fri, 19 Mar 2004 14:00:11 +0100
tom at replic8.net wrote:
> updated port, fixing many issues, made 'portlint -A' my friend.
>
> new version is here (old one removed):
> http://hannover.ccc.de/~e-moth/ports_net_netatalk-devel.tar.gz
> http://hannover.ccc.de/~e-moth/ports_net_netatalk-devel.tar.gz.md5
>
> MD5 (ports_net_netatalk-devel.tar.gz) = 8e60bbb33f5e7bb5df67d4f8b5ba0519
>
> please comment, thank you very much!
I still get FATAL errors with portlint -A.
README.html is a generated file and not part of a port.
Why don't you simply download 2.0 alpha2? Please use fixed snapshots
when possible. If you want to add extra patches, you can add them
as PATCHFILES, possibly conditionalized on WITH_CUPS_PATCH or
WITHOUT_CUPS_PATCH.
You should change the PKGNAMESUFFIX accordingly.
You might want to convert files/netatalk.sh to a rcNG script, which
should be easy if you are used to pkgsrc.
The WANT_AUTO* variables are somewhat deprecated, please use the
USE_AUTO equivaltents. Do you really need all those tools? Normally
packages contain a pregenerated configure script, so that only
GNU_CONFIGURE is necessary. Otherwise patching the configure
script doesn't make sense. You should not need to patch ltmain.sh
if you USE_LIBTOOL from the ports.
Where is it that you use perl?
I know that "See Netatalk's Makefile for more details on some of these
options." is from marcus@ port, but I don't consider this very helpful.
share/nls/POSIX
share/nls/en_US.US-ASCII
are not generated by your port, and shouldn't be part of the packing list.
There are still manpages in the packing list.
You should not remove user-editable configuration files, at least not
if they are edited by the user.
Please refer to the FreeBSD Porter's Handbook:
<http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html>
-Oliver
More information about the freebsd-ports-bugs
mailing list