unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ng0@n0.is
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: gnutls guile
Date: Fri, 17 May 2019 08:53:24 +0000	[thread overview]
Message-ID: <20190517085324.qhgmnn5nvnqpomhe@uptimegirl> (raw)
In-Reply-To: <87mujlefk5.fsf@elephly.net>

Hi Ricardo,

thanks for getting back to me.

One detail I'm still not clear about:
Ludovic said the guile bindings are maintained by Ludovic.
But recent activity in the guile parts is done by other people.
Since guix depends on this it's still okay to ask for help here,
but would it be more appropriate to report elsewhere? Or do you
still have some way to contribute changes back to GnuTLS?

Ricardo Wurmus transcribed 627 bytes:
> 
> Hi ng0,
> 
> > The original error post:
> > https://lists.gnutls.org/pipermail/gnutls-help/2019-February/004488.html
> >
> > I hope this is enough context to get a reply.
> 
> from the original post I see that you don’t expect that triplet.  From
> your last two emails I don’t see why you can’t just patch it out and be
> on your merry way.  I also don’t see why Netbsd would change the
> triplet.  You wrote “This happens to make the builds and filenames more
> predicatable”, but I guess you can just change this, no?
> 
> Have you attempted to stop the triplet from being changed?

No, this is done by pkgsrc facility, which targets more than just NetBSD.
Consequentially this would be against the pkgsrc guidelines (and probably
hard to do).
I think ( / hope ) I mentioned in my previous email(s) the location of
the mk file which handles this. The tl;dr is that this is at the core
of pkgsrc.
I can look into wether this is possible, but in my opinion there should
be an exception for pkgsrc: GnuTLS is not part of the base system, so
the only way to get GnuTLS (and its bindings) is via pkgsrc even on NetBSD;
ie pkgsrc is the defacto way to install gnutls with guile bindings.
I will gather more information, but
GSoC is upcoming and it might take some time until I get back to you.

In case I can provide more useful information in addition to asking the right
people wether this is possible, let me know.

Cheers,
ng0
 
> --
> Ricardo
> 

  reply	other threads:[~2019-05-17  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12  0:20 gnutls guile ng0
2019-03-13 17:59 ` ng0
2019-05-17  6:54   ` Ricardo Wurmus
2019-05-17  8:53     ` ng0 [this message]
2019-05-19 14:42       ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190517085324.qhgmnn5nvnqpomhe@uptimegirl \
    --to=ng0@n0.is \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).