unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Cássio Tavares" <cassio.ufg@gmail.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Guix Help Mailing List <help-guix@gnu.org>
Subject: Re: Packaging existing software for Guix
Date: Thu, 31 Mar 2022 22:23:24 +0000	[thread overview]
Message-ID: <CAJTCCxOg--V3XubFyss=v3Ri-Y3ZDkB21aV3giZ2fq1KrDCuTA@mail.gmail.com> (raw)
In-Reply-To: <87wngclnzd.fsf@contorta>

Thanks, Vagrant.


> For changes going into upstream Guix, generally yes. Because guix is
> functional package management, you need to know the hashes of your
> inputs in advance.
>
> The exception might be that some upstream software provides a guix.scm
> to be able to build from the current git checkout. For example, the GNU
> Mes project:
>
>   https://git.savannah.gnu.org/cgit/mes.git/tree/guix.scm
>

OK, I checked this scheme file, and it's just a four-line program, but I
don't get it. So, help me here ─ what is this *↓↓↓* `mes` code actually
doing?

(define %source-dir (dirname (current-filename)))
(add-to-load-path (string-append %source-dir "/guix"))
(use-modules (git mes))

mes.git


Thanks again,
Cássio

  reply	other threads:[~2022-03-31 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 14:22 Packaging existing software for Guix Cássio Tavares
2022-03-29 15:55 ` Ricardo Wurmus
2022-04-04 21:17   ` Cássio Tavares
2022-04-08  3:59     ` raingloom
2022-03-29 16:31 ` Vagrant Cascadian
2022-03-31 22:23   ` Cássio Tavares [this message]
2022-04-02 17:00     ` Bird
  -- strict thread matches above, loose matches on Subject: below --
2022-04-01  6:26 Liliana Marie Prikler
2022-04-01 13:21 ` Cássio Tavares

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='CAJTCCxOg--V3XubFyss=v3Ri-Y3ZDkB21aV3giZ2fq1KrDCuTA@mail.gmail.com' \
    --to=cassio.ufg@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=vagrant@debian.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. 
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).