unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: Development of GNU Guix and the GNU System distribution
	<guix-devel@gnu.org>
Subject: Re: [RFC] [Feature] In project `configuration.scm` allow dependencies to other repos with `configuration.scm`
Date: Tue, 19 Nov 2024 12:28:18 +0200	[thread overview]
Message-ID: <ZzxoQulRwCcKCc33@3900XT> (raw)
In-Reply-To: <CAFkJGRevnWs3H3wC8_Qa54q5ZDubr8=fhaKYn1UrXPBR+ygugA@mail.gmail.com>

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

On Mon, Nov 18, 2024 at 01:25:22PM -0500, Josh Marshall wrote:
> Hello all,
> 
> I have come across a use case that I don't find well addressed.  If I
> am not wrong (and I very well might be) it would be a feature which
> could be of great use.  First sent to a Nix channel, but I think the
> same applies here.
> 
> ```
> I want to use git repos with Nix Flakes in them directly as if they
> were package dependencies in another Flake. I can't seem to find good
> documentation for this. Is it even a thing? The purpose is to improve,
> but not impose perfection or slowdown, on developers or researchers as
> they Nix-ify their projects. The application is that I have a root
> project that needs to be put into a flake, which in turn has a number
> of other projects which are not Nix packages but could feasibly add a
> Nix Flake. The end goal is to be able to set up and package a project
> such that the end result is as easy to replicate for others as
> described here:
> https://obscuratur-in-arena.readthedocs.io/en/latest/A-good-way-to-set-up-your-python-project-using-Nix-Direnv-and-Poetry.html
> ```
> 
> I regret that I must again be someone who just throws more work
> demands into the ether.  The whole "I am finite" thing.

There are a number of projects (like shepherd) which are also setup to
function as a channel. And Guix has the ability for channels to depend
on other channels. So it would be possible to create a package in a
channel which depended on a specific branch (or commit) of shepherd as
it appeared upstream.  Is that the type of thing you mean?


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-11-19 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 18:25 [RFC] [Feature] In project `configuration.scm` allow dependencies to other repos with `configuration.scm` Josh Marshall
2024-11-19 10:28 ` Efraim Flashner [this message]
2024-11-19 16:41   ` Josh Marshall
2024-11-20 21:45     ` Ludovic Courtès
2024-11-20 23:59       ` Josh Marshall

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=ZzxoQulRwCcKCc33@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=joshua.r.marshall.1991@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).