On Mon, Jan 05, 2015 at 08:55:24PM +0100, Bruno Flueckiger wrote:
> On 05.01.2015 19:33, Ingo Schwarze wrote:
> >Hi,
> >
> >Antoine Jacoutot wrote on Mon, Jan 05, 2015 at 04:50:38PM +0100:
> >>On Mon, Jan 05, 2015 at 03:40:56PM +0000, Stuart Henderson wrote:
> >>>On 2015/01/05 16:30, Antoine Jacoutot wrote:
> >
> >>>>Why? We support gzipped manpages just fine.
> >
> >>>Consistency if nothing else..
> >
> >>That's only because we started supporting gzip'ed manpages
> >>not so long ago.
> >
> >Both man(1) and apropos(1) have been supporting them for years,
> >long before both were switched to the mandoc implementation.
> >
> >>And that no one bothered removing the patches. But for new ports,
> >>I see no reason to patch out for something we support.
> >
> >espie@ does, here is what he told me on June 13, 2014:
> >
> >:: Don't do it.
> >::
> >:: gzip manuals in packages are a bad idea.
> >:: They store a timestamp within the file proper.
> >::
> >:: This completely precludes the optimization I'm working on
> >:: wrt pkg_add and updates.
> >
> >Yours,
> > Ingo
> >
> Thanks for the valuable input. I've made good progress and I'm not
> almost at the point to send the port to the list. But there are two
> questions right now:
>
> 1. The port is a daemon. And a daemon needs a rc.d script. So I've
> created one according to
> http://www.openbsd.org/faq/ports/specialtopics.html#RcScripts
> I place it in pkg/udpxy.rc and run make plist. This gives me a
> complain:
>
> make-plist: Bogus element outside of every prefix: /etc/rc.d/udpxy
>
> I optimistically ignore it and continue with make package. But the
> script doesn't get included in the package. What step(s) am I missing to
> get script included into the package?
you need a special entry in PLIST like @rcscript ${RCDIR}/udpxy for the
script to be included in the package.
Landry