unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 45523@debbugs.gnu.org
Subject: [bug#45523] [PATCH 0/2] Update for frrouting & add libyang
Date: Wed, 30 Dec 2020 19:11:58 -0500	[thread overview]
Message-ID: <X+0XTrc+Rnc+o0pt@jasmine.lan> (raw)
In-Reply-To: <CAEwRq=ofLk7kYYM5uV6srU8Ce6cF7W+xVwQa50Ah2tGEVX7Y7Q@mail.gmail.com>

On Tue, Dec 29, 2020 at 11:17:54AM +0100, Vincent Legoll wrote:
> I was not sure if I should have made pcre a
> propagated-input in libyang instead of adding
> it to frrouting or something like that.

libyang includes pcre in the Requires.private field of libyang.pc.
According to the 'package reference' section of the Guix manual,
inputs should be propagated in this case:

https://guix.gnu.org/manual/en/html_node/package-Reference.html

> I used the BSD-3 license for libyang, this should
> be checked as I am not sure this is the right one.

(guix licenses) includes links to authoritative sources on licenses:

https://git.savannah.gnu.org/cgit/guix.git/tree/guix/licenses.scm#n167

You can check the package's LICENSE file against those resources.




  parent reply	other threads:[~2020-12-31  0:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 10:17 [bug#45523] [PATCH 0/2] Update for frrouting & add libyang Vincent Legoll
2020-12-29 10:20 ` [bug#45523] [PATCH 1/2] gnu: Add libyang Vincent Legoll
2020-12-29 10:20   ` [bug#45523] [PATCH 2/2] gnu: frrouting: Update to 7.5 Vincent Legoll
2020-12-31  0:11 ` Leo Famulari [this message]
2021-01-05 10:57 ` [bug#45523] [PATCH 1/2] gnu: Add libyang Vincent Legoll
2021-01-05 10:57   ` [bug#45523] [PATCH 2/2] gnu: frrouting: Update to 7.5 Vincent Legoll
2021-02-20 18:49   ` [bug#45523] [PATCH 1/2] gnu: Add libyang Leo Famulari
2021-02-20 19:02     ` Vincent Legoll
2021-02-20 23:04       ` bug#45523: " Leo Famulari
2021-01-05 11:00 ` [bug#45523] new patch set Vincent Legoll

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=X+0XTrc+Rnc+o0pt@jasmine.lan \
    --to=leo@famulari.name \
    --cc=45523@debbugs.gnu.org \
    --cc=vincent.legoll@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).