all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: slg <0x2d@disroot.org>, 49123@debbugs.gnu.org
Subject: [bug#49123] [PATCH 24/24] gnu: Add mirage.
Date: Mon, 21 Jun 2021 18:10:23 +0200	[thread overview]
Message-ID: <51c8cef20e8358e6c7d5d8ae048ddbc1af66cd73.camel@telenet.be> (raw)
In-Reply-To: <20210620010742.4259-24-0x2d@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]

slg via Guix-patches via schreef op za 19-06-2021 om 22:07 [-0300]:
> * gnu/packages/messaging.scm (mirage): New variable.
> ---
>  gnu/packages/messaging.scm | 96 ++++++++++++++++++++++++++++++++++++++
>  1 file changed, 96 insertions(+)
> 
> diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
> index fe678d89fd..a8cdd90f57 100644
> --- a/gnu/packages/messaging.scm
> +++ b/gnu/packages/messaging.scm
> @@ -2997,4 +2997,100 @@ API.  Mattermost is not required.")
>      (home-page "https://github.com/42wim/matterbridge")
>      (license license:asl2.0)))
>  
> +(define-public mirage
> +  (package
> +    ;; (inherit qtsvg)
> +    (name "mirage")
> +    (version "0.7.1")
> +    (source (origin
> +              (method git-fetch)
> +              (uri (git-reference
> +                    (url "https://github.com/mirukana/mirage")
> +                    (commit (string-append "v" version))
> +                    (recursive? #t)))
> +              (file-name (git-file-name name version))
> +              (sha256
> +               (base32
> +                "0j7gdg2z8yg3qvwg9d9fa3i4ig231qda48p00s5gk8bc3c65vsll"))))
> +    (build-system gnu-build-system)
> +    (native-inputs
> +     `(("python" ,python-wrapper)))
> +    (propagated-inputs [ plenty of inputs ])

If possible, try to move some of these to 'inputs'.
Of course, mirage still needs to find all these python
libraries, so you may need to add a post-install phase
(after/before qt-wrap shouldn't mattr) doing appropriate
‘wrap-program' calls -- yes, an already wrapped program
can be wrapped again. I think. I'd presume the effects are
cumulative, not sure though.

Why? Keeping ‘propagated-inputs’ minimal reduces profile
pollution, so the profile contains less, so generating the
profile takes less time. This also reduces the chance
of version conflicts. (E.g., guile and stalin cannot be
installed in the same profile because they propagate
different versions of libgc.)

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-06-21 16:11 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 23:17 [bug#49123] [PATCH 0/24] Add mirage slg via Guix-patches via
2021-06-20  1:07 ` [bug#49123] [PATCH 01/24] gnu: Add pyotherside slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 02/24] gnu: libolm: Add python bindings output slg via Guix-patches via
2021-06-21 15:44     ` Maxime Devos
2021-07-04 14:41       ` slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 03/24] gnu: libolm: Update to 3.2.4 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 04/24] gnu: Add python-html-sanitizer slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 05/24] gnu: Add python-filetype slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 06/24] gnu: Add python-logbook slg via Guix-patches via
2021-07-19 12:18     ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 07/24] gnu: python-unpaddedbase64: Update to 2.1.0 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 08/24] gnu: python-pycryptodome: Update to 3.10.1 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 09/24] gnu: python-hyperframe: Update to 6.0.1 slg via Guix-patches via
2021-07-24 15:22     ` Maxime Devos
2021-07-24 18:30       ` Vinicius Monego
2021-07-24 18:42         ` [bug#48263] " Maxime Devos
2021-08-12  0:04           ` Vinicius Monego
2021-06-20  1:07   ` [bug#49123] [PATCH 10/24] gnu: python-h2: Update to 4.0.0 slg via Guix-patches via
2021-07-18 16:15     ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 11/24] gnu: python-h11: Update to 0.12.0 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 12/24] gnu: python-future: Update to 0.18.2 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 13/24] gnu: python-socks: Update to 1.2.4 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 14/24] gnu: python-aiohttp-socks: Update to 0.6.0 slg via Guix-patches via
2021-07-20 13:11     ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 15/24] gnu: Add python-aioresponses slg via Guix-patches via
2021-07-21 13:44     ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 16/24] gnu: python-hpack: Update to 4.0.0 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 17/24] gnu: Add python-matrix-nio slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 18/24] gnu: python-pymediainfo: Update to 5.1.0 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 19/24] gnu: python-watchgod: Update to 0.7 slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 20/24] gnu: Add python-plyer slg via Guix-patches via
2021-06-21 15:53     ` Maxime Devos
2021-07-04 16:45       ` slg via Guix-patches via
2021-07-06 10:28         ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 21/24] gnu: Add python-baron slg via Guix-patches via
2021-06-20  1:07   ` [bug#49123] [PATCH 22/24] gnu: Add python-redbaron slg via Guix-patches via
2021-07-15 10:13     ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 23/24] gnu: Add python-hsluv slg via Guix-patches via
2021-07-15 13:31     ` Maxime Devos
2021-06-20  1:07   ` [bug#49123] [PATCH 24/24] gnu: Add mirage slg via Guix-patches via
2021-06-21 16:10     ` Maxime Devos [this message]
2021-07-19 12:05   ` [bug#49123] [PATCH 01/24] gnu: Add pyotherside Maxime Devos

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=51c8cef20e8358e6c7d5d8ae048ddbc1af66cd73.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=0x2d@disroot.org \
    --cc=49123@debbugs.gnu.org \
    /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.