From: sirgazil via Guix-patches via <guix-patches@gnu.org>
To: 31285 <31285@debbugs.gnu.org>
Subject: [bug#31285] [PATCH 0/1] guix: Add git-fetch/impure.
Date: Sat, 18 Apr 2020 15:54:04 +0000 [thread overview]
Message-ID: <1718dff34ac.cc32d28414025.6904503667509437602@zoho.com> (raw)
In-Reply-To:
Hi,
I feel the same as Chris. I started doing some packaging this year, and really felt downhearted when I found there was no support for package definitions with SSH authenticated git repositories (for private use, of course).
In my case, I need this for two reasons:
* I want to use Guix channels for experimental packages, prototypes and pre-alpha software that should be available for some people only.
* I want to use Guix channels for production-ready packages of in-house tools that are only useful for private businesses.
In both cases, the channels and software sources would be in Git repositories hosted by third-parties like GitLab, BitBucket, etc., which provide SSH authentication.
There are some comments already about Chris' patch in another bug report (issues.guix.gnu.org/issue/31284). I agree that "git-fetch/impure" must not be used in Guix's official channel(s), but I'd like Guix to include it in its API for use in private channels.
I think having this functionality would make it even easier to adopt the GNU Guix in mainstream culture.
---
https://sirgazil.bitbucket.io/
next prev parent reply other threads:[~2020-04-18 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 8:15 [bug#31285] [PATCH 0/1] guix: Add git-fetch/impure Chris Marusich
2018-04-27 8:26 ` [bug#31285] [PATCH 1/1] " Chris Marusich
2018-04-30 2:49 ` Chris Marusich
2020-12-01 18:06 ` zimoun
2020-04-18 15:54 ` sirgazil via Guix-patches via [this message]
2020-10-22 0:44 ` [bug#31285] [PATCH 0/1] " Luis Felipe via Guix-patches via
2021-07-14 9:23 ` bug#31285: " Chris Marusich
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=1718dff34ac.cc32d28414025.6904503667509437602@zoho.com \
--to=guix-patches@gnu.org \
--cc=31285@debbugs.gnu.org \
--cc=sirgazil@zoho.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).