On Fri, Aug 13, 2021 at 06:13:33PM +0200, Theo Buehler wrote:
>
> So I suggest that we go with the diff below that removes requiring ./
> unless someone explains why it should be kept. I'll then strip the
> ./ from the Go ports and switch from to "x" in a few Rust ports.
ok semarie@
> Index:
On Fri, 13 Aug 2021 18:13:33 +0200, Theo Buehler
wrote:
> On Fri, Aug 13, 2021 at 10:35:13AM +0200, Sebastien Marie wrote:
> > On Thu, Aug 12, 2021 at 04:48:13PM +0200, Theo Buehler wrote:
> > > Now that a few Rust ports use crates.inc, I think we should teach
> > > portcheck about it. I
On Fri, Aug 13, 2021 at 10:35:13AM +0200, Sebastien Marie wrote:
> On Thu, Aug 12, 2021 at 04:48:13PM +0200, Theo Buehler wrote:
> > Now that a few Rust ports use crates.inc, I think we should teach
> > portcheck about it. I didn't use @(|) for the pattern since the result
> > seemed less
On Thu, Aug 12, 2021 at 04:48:13PM +0200, Theo Buehler wrote:
> Now that a few Rust ports use crates.inc, I think we should teach
> portcheck about it. I didn't use @(|) for the pattern since the result
> seemed less readable.
>
> Two things:
>
> A few Rust ports use '.include ' I'll switch
Theo Buehler writes:
> Now that a few Rust ports use crates.inc, I think we should teach
> portcheck about it. I didn't use @(|) for the pattern since the result
> seemed less readable.
Once there is a pattern to follow, I'll apply it to Haskell
ports. Luckily there are few of them. I'll
Now that a few Rust ports use crates.inc, I think we should teach
portcheck about it. I didn't use @(|) for the pattern since the result
seemed less readable.
Two things:
A few Rust ports use '.include ' I'll switch those to using
'.include "crates.inc"' so the current directory is searched
