From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining GNU Jami package for Guix
Date: Sun, 20 Oct 2019 00:37:19 +0200 [thread overview]
Message-ID: <20191020003719.291dcf2c@kompiuter> (raw)
In-Reply-To: <87sgnojw4f.fsf@elephly.net>
On Sat, 19 Oct 2019 22:52:58 +0200
Ricardo Wurmus <rekado@elephly.net> wrote:
> We always try to unbundle libraries, because that ensures that all
> packages benefit from security fixes.
>
Great, so I have to package everything recursively :)
Just to make it clear, because I'm a bit unfamiliar with build systems
and the package API - will packing every library pjproject uses and
just adding it in the "inputs" field make building possible, or will I
have to do magic and copy built packages into "third_party" folder in
the pjproject source tree?
Also what if pjproject (or any package I want to update) depends on a
specific version of a library? Should I just update the package, or
should I add a separate version of the library?
Jan Wielkiewicz
next prev parent reply other threads:[~2019-10-19 22:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 18:56 Maintaining GNU Jami package for Guix Jan
2019-10-18 19:28 ` Marius Bakke
2019-10-19 9:02 ` Pierre Neidhardt
2019-10-19 20:38 ` Jan Wielkiewicz
2019-10-19 20:52 ` Ricardo Wurmus
2019-10-19 22:37 ` Jan [this message]
2019-10-20 11:14 ` Ricardo Wurmus
2019-10-20 11:51 ` Pierre Neidhardt
2019-10-20 11:48 ` Pierre Neidhardt
2019-10-25 15:03 ` Pierre Neidhardt
2019-10-25 19:44 ` Jan Wielkiewicz
2019-10-26 10:12 ` Pierre Neidhardt
2019-10-26 23:24 ` Jan Wielkiewicz
2019-10-28 7:53 ` Pierre Neidhardt
2019-10-27 18:13 ` Jan Wielkiewicz
2019-10-27 18:18 ` Pierre Neidhardt
2019-10-27 19:23 ` Jan Wielkiewicz
2019-10-27 21:52 ` Jan Wielkiewicz
2019-10-31 20:19 ` Jan Wielkiewicz
2019-10-31 21:37 ` Pierre Neidhardt
2019-10-31 22:26 ` Marius Bakke
2019-11-01 12:01 ` Jan Wielkiewicz
2019-11-01 19:02 ` Pierre Neidhardt
2019-11-01 20:42 ` Jan Wielkiewicz
2019-11-02 9:38 ` Pierre Neidhardt
2019-11-03 16:37 ` Marius Bakke
2019-11-03 17:43 ` Jan
2019-11-03 18:06 ` Marius Bakke
2019-11-01 12:29 ` Jan Wielkiewicz
2019-11-01 19:01 ` Pierre Neidhardt
2019-11-01 23:16 ` Jan Wielkiewicz
2019-11-03 10:15 ` Pierre Neidhardt
2019-11-03 10:54 ` Jan Wielkiewicz
2019-11-04 10:02 ` Gábor Boskovits
2019-11-03 10:59 ` Jan Wielkiewicz
2019-11-03 17:07 ` Marius Bakke
2019-11-03 17:47 ` Jan
2019-11-03 18:12 ` Marius Bakke
2019-11-03 18:27 ` Jan
2019-11-03 18:52 ` Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191020003719.291dcf2c@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.