unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: David Dashyan <mail@davie.li>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Bug? Importing (gnu rest ...) fails due to lack of patch files on build side.
Date: Tue, 27 Apr 2021 19:36:18 +0200	[thread overview]
Message-ID: <87d89701159f5d0213713a70b9c08928ae91c647.camel@telenet.be> (raw)
In-Reply-To: <87k0onoe1f.fsf@davie.li>

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

David Dashyan schreef op di 27-04-2021 om 20:03 [+0300]:
> 
> Hello, Maxime!
> 
> > No, it is not supposed to work!  Only guix/build/... and
> > gnu/build/utils/...  (and maybe others I forgot) are supposed to be
> > imported, so source-module-closure excludes other modules.  The reason
> > is that gnu/packages/*.scm are supposed to be changeable without
> > causing any change in derivation hash (and therefore resulting in
> > rebuilds).
> Ah, great! I'm glad I got definitive answer to this question.  But I
> don't get the last sentence.  Changeable when?  You mean that by
> including (gnu package ...) in inputs of a derivation change in
> gnu/package/*scm files will cause change of derivation hash?

If you mean:
All package, services, etc ... derivations that include the (gnu packages ...)
module (and its dependencies) would have a change in derivation hash,
then yes.

> But why it is a problem for service derivations?

It guess for service derivations (FWIW, that's not an ‘official’ term, I think),
this isn't much of a problem.  I still recommend using
(with-extensions (list guix) ...) or similar though (with the caveat that
the 'guix' package isn't always the latest guix, so you may want to consider
inferiors or something).

> As I understand it won't cause
> change in other package derivations hashes propagating down the graph.
> Service derivation sits on the leaf of dependency graph.  Or I missing
> something?
No, that's correct.

> > > Some context to why am I doing it in the first place.  I found this
> > > out while I was implementing "guix-cloud-init" service.  The service
> > > to simplify guix deployment to digialocean, aws and others.
> > > Cloud-init is widely used way of configuring cloud vm instances and
> > > it works by providing metadata via mounted storage or link-local
> > > address http endpoint.  This includes ip addresses, devices, ssh keys
> > > etc...  So given you have a guix image with guix-cloud-init service
> > > you can upload to your cloud and it will "just work". :)
>
> Do you know about "guix deploy"?
> [Plenty of text]

I'm not familiar with clouds that aren't

 aerosol consisting of a visible mass of minute liquid droplets, frozen crystals,
 or other particles suspended in the atmosphere of a planetary body or similar space.
 (Source: <https://en.wikipedia.org/wiki/Cloud>, accessed 2021)

so I'm afraid I don't have much to say here, but your idea of skipping Debian
seems better than is done currently!

Greetings,
Maxime

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

      reply	other threads:[~2021-04-27 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  9:48 Bug? Importing (gnu rest ...) fails due to lack of patch files on build side David Dashyan
2021-04-13 22:10 ` David Dashyan
2021-04-16 14:10   ` Joshua Branson
2021-04-17 21:39     ` David Dashyan
2021-04-25 16:24 ` Maxime Devos
2021-04-27 17:03   ` David Dashyan
2021-04-27 17:36     ` Maxime Devos [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=87d89701159f5d0213713a70b9c08928ae91c647.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=help-guix@gnu.org \
    --cc=mail@davie.li \
    /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.
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).