unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Jean-Baptiste Note <jean-baptiste.note@m4x.org>,
	41013-done@debbugs.gnu.org
Subject: bug#41013: [PATCH] Add gccmakedep util
Date: Tue, 05 May 2020 19:13:42 +0200	[thread overview]
Message-ID: <878si6z4mx.fsf@devup.no> (raw)
In-Reply-To: <87d07nbcmy.fsf@m4x.org>

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

Jean-Baptiste Note <jean-baptiste.note@m4x.org> writes:

> Dear Guix maintainers,
>
> I'm attempting to package x2go, and gccmakedep from the xorg utils is
> required for the build.
>
> This is therefore an attempt to package it -- so as to be able to use it
> as native-input -- even though it is a deprecated tool.
>
> There are two flavors of the patch:
>
> - a -tar version which relies on a standard xorg mirror for download,
>   and does not need the maintainer tools to build. Unfortunately guix
>   lint reports a problem in that the tarball is not mirrored on software
>   heritage.
>
> - a -git version which is a bit more convoluted to build (requires
>   maintainer tools as native-inputs: autoconf, automake, xorg macros),
>   but with no failure in guix lint.
>
> Please also note that /some/ elements from this xorg subdirectory are
> prefixed with util- -- i've chosen not to include it here.
>
> Please pick your choose, and let me know how to proceed!

Thanks!  I applied the bootstrapped variant, with minor cosmetic changes
to the description and fixed indentation of the source section.

Software Heritage can currently only archive Git repositories, so the
lint warning is arguably misleading.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2020-05-05 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 20:53 [bug#41013] [PATCH] Add gccmakedep util Jean-Baptiste Note
2020-05-05 17:13 ` Marius Bakke [this message]

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=878si6z4mx.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=41013-done@debbugs.gnu.org \
    --cc=jean-baptiste.note@m4x.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 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).