unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Circular dependency with LDC and Phobos
Date: Fri, 25 Dec 2015 19:19:22 +0100	[thread overview]
Message-ID: <20151225181922.GB27096@thebird.nl> (raw)
In-Reply-To: <871taapiep.fsf@gnu.org>

On Fri, Dec 25, 2015 at 06:06:22PM +0100, Roel Janssen wrote:
> > $ git submodule update -i
> 
> I think this specific case can be easily solved by the LDC developers by
> providing proper tarballs with the *complete* source code to build LDC.

Asking upstream developers may or may not solve it, depending on
whether they honour our ideas. But there are more cases, e.g.,
freebayes, sambamba and the list goes on of packages that use git
recursive modules as part of their build instructions.

Either we fix git recurse submodules - and I think there is no reason
we should not - or we allow importing multiple sources before the
build phase.

My question is how to do this last one in the best way because I don't
see any precedents in the gnu/package sources.

I would like to hear the thoughts of the Guix architects. What would
be the preferred policy:

1. Write a source package for phobos and make it available in the build phase of
   the other package ldc
2. Fix git recursive downloads
3. Allow multiple source downloads in one package

Pj.
-- 

  reply	other threads:[~2015-12-25 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-25 16:51 Circular dependency with LDC and Phobos Pjotr Prins
2015-12-25 17:06 ` Roel Janssen
2015-12-25 18:19   ` Pjotr Prins [this message]
2015-12-25 21:18     ` Ricardo Wurmus
2015-12-26  5:04       ` Pjotr Prins

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=20151225181922.GB27096@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=roel@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 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).