New port, what's next?

[Kevin Oberman]

On Fri, Apr 11, 2014 at 2:13 AM, Dominic Fandrey <kamikaze at bsdforen.de>wrote:

> On 10/04/2014 20:28, Baptiste Daroussin wrote:
> > On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote:
> >>
> >> On 10/04/2014 18:53, Helmut Schneider wrote:
> >>> I created a new port, Typo3-LTS. The tgz contains
> >>>
> >>> - Makefile
> >>> - distinfo
> >>> - pkg-plist
> >>> - pkg-descr
> >>> - a diff from www/typo3
> >>>
> >>> The file has ~150kB so I assume it's to big for a PR.
> >>
> >> I assume the bulk of that is the pkg-plist. The largest pkg-plist
> >> in the ports tree is 4M. In my opinion huge plists should be dynamically
> >> generated, but in your case I'd just I'd just temp-host the file
> >> somewhere and file a PR with a link and a checksum.
> >>
> >> Regards
> >>
> >
> > ...
> > autoplist is dangerous because we have no way to control that what is
> package is
> > what the maintainer expect to be packaged! therefore we often end up with
> > unoticed problems
>
> The majority of problems I used to have as a port maintainer stemmed from
> fiddling with plists. I.e. my experience is the opposite, manual plists
> lead to errors. Autogenerated plists (which I use in most cases, because
> dynamic ones are against policy) have reduced the amount of mistakes I make
> tremendously.
>

I find redports is an effective way to check  on plists. I found that it
was the best way to catch errors, especially on one port that had a many
hundred line long plist.
-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com