unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Niklas Schmidt <snlabs@posteo.net>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: help-guix@gnu.org
Subject: Re: manifest.scm - Howddya get specific commit 4 package?
Date: Thu, 13 Jan 2022 19:19:58 +0000	[thread overview]
Message-ID: <YeB7XjGOt0WcrRUD@posteo.de> (raw)
In-Reply-To: <b87d74f8-96f0-b458-8787-5f1a69e042b5@rixotstudio.cz>

Hello Jacob,

I would like to point you to the section 2.1.5.3 Inheritance of the 
cookbook:
https://guix.gnu.org/cookbook/en/guix-cookbook.html#Inheritance

There it says:

   All unspecified fields are inherited from the parent package. This is
   very convenient to create alternative packages, for instance with
   different source, version or compilation options. 

So I usually create my own package module, specify a new package that 
inherits the package I'm interested in and give it another unique name, 
say my-freecad. Then I specify my-freecad in the manifest and use the -L 
or --load-path= flag with the file system path of own package module to 
invoke guix package, guix shell, and so on.

Hope that get's you somewhere.

To be exact, I have not used this technique for obtaining a package a 
specific commit, but for different versions. I see no reason it wouldn't 
work for this scenario as well, though.


Greetings
Niklas


On Tue, Jan 11, 2022 at 00:18:01 +0000, Jacob Hrbek wrote:
>I need FreeCAD 07c51f1b2ce62b1c770ffde8a7c40899a8abf846 -> How can i 
>get it through manifest.scm without using guix install freecad 
>--with-commit=freecad=07c51f1b2ce62b1c770ffde8a7c40899a8abf846 ?


      reply	other threads:[~2022-01-13 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  0:18 manifest.scm - Howddya get specific commit 4 package? Jacob Hrbek
2022-01-13 19:19 ` Niklas Schmidt [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=YeB7XjGOt0WcrRUD@posteo.de \
    --to=snlabs@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=kreyren@rixotstudio.cz \
    /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).