Re: knot-resolver posibility?

[Greg Troxel <gdt%lexort.com@localhost>]

Marcin Gondek <drixter%e-utp.net@localhost> writes:

> I know but it's quite complicated for me (still learning), trying with some partial success, I'm looking for someone more experienced to continue or make it from scratch -> I would be very grateful.
> As far I've properly understood, we need buildlink3.mk for knot, I've submitted this as bug pkg/58647.

That's totally fine to ask for help.

> What I've done so far:

(First, I am not the knot fixer you are looking for.)

I find it much easier to look at things in wip.  Pulling patches out of
email is confusing and harder.

So, if you want help, I would suggest:

  get a wip account

  create a knot package in wip with the changes you think you need,
  trying hard to be minimal, in that 'diff -ur' from pkgsrc to wip is
  only things you intend to change.

  create a knot-resolver package

  get as far as you can, and then ask for help, pointing to the above


> File: net/knot/buildlink3.mk (bug pkg/58647)

> # $NetBSD$
> BUILDLINK_TREE+=        knot
> .if !defined(KNOT_BUILDLINK3_MK)
> KNOT_BUILDLINK3_MK:=
> BUILDLINK_API_DEPENDS.knot+=    knot>=3.3.8
> BUILDLINK_PKGSRCDIR.knot?=      ../../net/knot
> .endif  # KNOT_BUILDLINK3_MK
> BUILDLINK_TREE+=        -knot

I hope someone who knows something about knot will add that, but it
looks straightforward.  It seems the bug has been assigned to the
MAINTAINER.

But this should not keep you from making progress.

> File: wip/knot-resolver/patches/patch-utils_client_kresc.c

I don't find this in wip.  maybe you need to rebase and push?


In case you are wondering, it's ok to have broken packages in wip.
Please do create a TODO file that lists all the things you know need
fixing (briefly; checklist vs howto!).