Hi,
On Thu, Mar 08, 2018 at 07:43:24PM +0100, Caspar Schutijser wrote:
> On Thu, Mar 08, 2018 at 01:14:38PM +0100, Klemens Nanni wrote:
> > shellcheck.1 is included in the source tarball right next to the
> > markdown source.
>
> You're right. I was looking at the git repository of the project, n
On Thu, Mar 08, 2018 at 07:43:24PM +0100, Caspar Schutijser wrote:
> On Thu, Mar 08, 2018 at 01:14:38PM +0100, Klemens Nanni wrote:
> > shellcheck.1 is included in the source tarball right next to the
> > markdown source.
>
> You're right. I was looking at the git repository of the project, not
>
Hi,
On Thu, Mar 08, 2018 at 01:14:38PM +0100, Klemens Nanni wrote:
> shellcheck.1 is included in the source tarball right next to the
> markdown source.
You're right. I was looking at the git repository of the project, not
at WRKSRC. Sorry about that, lesson learned, thanks. Attached is an
update
On Thu, Mar 08, 2018 at 08:20:28AM +0100, Caspar Schutijser wrote:
> Hi,
>
> On Thu, Mar 08, 2018 at 12:21:26AM +0100, Klemens Nanni wrote:
> > The manual page is missing. With it installed OK kn.
>
> Unfortunately, upstream does not provide a real man page. The thing
> closest to a man page is a
On Thu, Mar 08, 2018 at 11:05:53AM +, Stuart Henderson wrote:
> On 2018/03/08 08:20, Caspar Schutijser wrote:
> > Hi,
> >
> > On Thu, Mar 08, 2018 at 12:21:26AM +0100, Klemens Nanni wrote:
> > > The manual page is missing. With it installed OK kn.
> >
> > Unfortunately, upstream does not prov
On 2018/03/08 08:20, Caspar Schutijser wrote:
> Hi,
>
> On Thu, Mar 08, 2018 at 12:21:26AM +0100, Klemens Nanni wrote:
> > The manual page is missing. With it installed OK kn.
>
> Unfortunately, upstream does not provide a real man page. The thing
> closest to a man page is a file called shellche
Hi,
On Thu, Mar 08, 2018 at 12:21:26AM +0100, Klemens Nanni wrote:
> The manual page is missing. With it installed OK kn.
Unfortunately, upstream does not provide a real man page. The thing
closest to a man page is a file called shellcheck.1.md, a Markdown
document that somewhat looks like a man
On Wed, Mar 07, 2018 at 11:22:31PM +0100, Matthias Kilian wrote:
> On Wed, Feb 21, 2018 at 08:15:06PM +0100, Caspar Schutijser wrote:
> > On Mon, Feb 19, 2018 at 10:16:09PM +0100, Caspar Schutijser wrote:
> > > The above comments have been addressed in the new tarball.
> >
> > Attached is a new ta
Hi,
On Wed, Feb 21, 2018 at 08:15:06PM +0100, Caspar Schutijser wrote:
> On Mon, Feb 19, 2018 at 10:16:09PM +0100, Caspar Schutijser wrote:
> > The above comments have been addressed in the new tarball.
>
> Attached is a new tarball. I took an even closer look at the devel/cpphs
> port. The most
On Mon, Feb 19, 2018 at 10:16:09PM +0100, Caspar Schutijser wrote:
> The above comments have been addressed in the new tarball.
Attached is a new tarball. I took an even closer look at the devel/cpphs
port. The most important change is that the -main package does not have
that many RUN_DEPENDS any
(Forgot to CC ports@)
Hi Matthias,
Thanks for your clear feedback!
On Sun, Feb 18, 2018 at 10:46:07PM +0100, Matthias Kilian wrote:
> I don't know how useful the library is,
I actually have no idea about that as well, to be honest. I'm mostly
interested in the shellcheck utility.
> but it sho
Oh, there's also no WANTLIB entry. You should run make
port-lib-depends-check after building the port.
Ciao,
Kili
Hi,
On Sun, Feb 18, 2018 at 11:40:53AM +0100, Caspar Schutijser wrote:
> Attached is a new port: devel/hs-ShellCheck, a shell script analysis
> tool. It depends on textproc/hs-json for which I just sent a new port
> because it is not in the ports tree yet.
>
> This port provides both a utility (b
On Sun, Feb 18, 2018 at 10:40:53AM +, Caspar Schutijser wrote:
> This port provides both a utility (bin/shellcheck), and a Haskell
> library. Should I split up the port into -main and -lib subpackages,
> just like x11/xmonad? Another approach is to let the user use cabal
> to get the library,
14 matches
Mail list logo
