unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: Mathieu OTHACEHE <m.othacehe@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Build custom packages with cuirass.
Date: Mon, 23 Jan 2017 00:42:32 +0100	[thread overview]
Message-ID: <87h94qpspj.fsf@gnu.org> (raw)
In-Reply-To: <87shobkseu.fsf@gmail.com> (Mathieu OTHACEHE's message of "Sun, 22 Jan 2017 16:47:53 +0100")

Hi,

Mathieu OTHACEHE <m.othacehe@gmail.com> writes:

> I'm trying to use cuirass to build all the packages of my current
> manifest on top of guix master periodically.
>
> Some of my packages are custom, so I need cuirass to be aware of
> GUIX_PACKAGE_PATH env variable.
>
> The only way I found is to patch cuirass service (cf. following patch).
> Is this a good idea ? Is someone doing this kind of stuff here ?

A quick and dirty way to fix your issue would be to add the absolute
base directory name for your custom package modules in the '#:load-path'
part of you specification.  However this will only work if your modules
names are '(gnu packages ...)'.

I guess Cuirass should handle this use case with '-L', '--load-path'
command line arguments like what 'guix build' does.  WDYT?

Would you be interested in implementing this?

Thanks.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

  reply	other threads:[~2017-01-22 23:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 15:47 Build custom packages with cuirass Mathieu OTHACEHE
2017-01-22 23:42 ` Mathieu Lirzin [this message]
2017-01-23  8:57   ` Mathieu OTHACEHE
2017-01-24 18:41     ` Mathieu Lirzin

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=87h94qpspj.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@gmail.com \
    /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).