Date: Wed, 30 Nov 2011 23:20:07 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-rc@freebsd.org, Ruslan Mahmatkhanov <cvs-src@yandex.ru> Subject: Re: rc-script review request Message-ID: <CAGH67wSXFq_1PA_HdYcMZg9QDJ0QMy4OoGQBcwdkVv-OdV9wYA@mail.gmail.com> In-Reply-To: <4ED71CE1.2010101@FreeBSD.org> References: <4ED66DCB.1040102@yandex.ru> <CADLo83-RR945MKbdvpdghHsHpO1_MA4OA21WkA_3xCTjOOhDsQ@mail.gmail.com> <4ED67B8F.50109@yandex.ru> <4ED6BE87.4060408@FreeBSD.org> <CAGH67wSwdbmsYQeeBbqATwx-WhMxNugVqY-cUo%2BEzxOz=N830A@mail.gmail.com> <4ED71CE1.2010101@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 30, 2011 at 10:21 PM, Doug Barton <dougb@freebsd.org> wrote: > On 11/30/2011 17:14, Garrett Cooper wrote: >> =A0 =A0 Crazy thought -- should a script be made for rc scripts, similar >> to portcheck? I meant portlint, BTW.. not portcheck :). > I look forward to reviewing your patches to implement this feature. :) Yipes... I have some work ahead of me. portlink is 3k lines of perlness... > Seriously though, I've thought about it, but the problem is that the > number of variables is really high, and unlike port Makefiles there are > very few standard elements that exist in a predetermined order. Well, yeah.. you can't catch everything, but it wouldn't hurt to catch basic issues so you wouldn't have to be bothered to review first drafts of code. > OTOH, I'd be happy to be proven wrong. Thanks! -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wSXFq_1PA_HdYcMZg9QDJ0QMy4OoGQBcwdkVv-OdV9wYA>