all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "muradm" <mail@muradm.net>
Cc: 56858@debbugs.gnu.org
Subject: [bug#56858] [PATCH] gnu: libcgroup: Update to 2.0.2.
Date: Mon, 01 Aug 2022 10:02:30 +0100	[thread overview]
Message-ID: <CLUKJUTJOXGZ.1WQDO9AYVGJJB@guix-aspire> (raw)
In-Reply-To: <87sfmgplez.fsf@muradm.net>

On Mon Aug 1, 2022 at 6:42 AM BST, muradm wrote:
> Is there a guideline where home-page should be? I find it more
> DRY when reusing.
Almost every package in Guix puts it directly above synopsis, though
you do have a point about DRY.

> Their repo is not suitable for building from, instead
> they release sources manually.
Looks okay to me: <https://github.com/libcgroup/libcgroup/tree/v2.0.2>
But there is a problem with vendoring googletest, it seems. You'll want
to use the system's googletest, and (recursive? #t) in the git-reference
to clone the tests repo. Also, the tarball seems to contain pregenerated
autotools files, which are discouraged by Guix.


    -- (




  reply	other threads:[~2022-08-01  9:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 15:29 [bug#56858] [PATCH] gnu: libcgroup: Update to 2.0.2 muradm
2022-07-31 21:48 ` ( via Guix-patches via
2022-08-01  5:42   ` muradm
2022-08-01  9:02     ` ( via Guix-patches via [this message]
2022-08-01  9:06       ` ( via Guix-patches via
2022-08-01 13:13       ` muradm
2022-08-09 15:37       ` Ludovic Courtès
2022-08-09 20:29         ` muradm
2022-08-23 21:10           ` [bug#56858] [PATCH v2] " muradm
2022-08-31 10:38             ` bug#56858: " Ludovic Courtès
2022-08-04  5:55   ` [bug#56858] [PATCH] " 宋文武 via Guix-patches via

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=CLUKJUTJOXGZ.1WQDO9AYVGJJB@guix-aspire \
    --to=guix-patches@gnu.org \
    --cc=56858@debbugs.gnu.org \
    --cc=mail@muradm.net \
    --cc=paren@disroot.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.