From: Xinglu Chen <public@yoctocell.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 51509@debbugs.gnu.org
Subject: [bug#51509] [PATCH] doc: Mention Hg support for 'guix import cran' and some caveats.
Date: Sun, 19 Dec 2021 10:04:42 +0100 [thread overview]
Message-ID: <875yrlothx.fsf@disroot.org> (raw)
In-Reply-To: <87ilweot1x.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Hi,
On Sat, Nov 27 2021, Ricardo Wurmus wrote:
> Hi,
>
>> * guix.texi (Invoking guix import): Mention support for
>> Mercurial repositories
>> for the CRAN importer, and some caveats with the Git and
>> Mercurial backends.
>> ---
>> Prompted by Ricardo’s comments on the “Accuracy of importers”
>> thread:
>>
>> <https://yhetil.org/guix-devel/87mtmq7pes.fsf@disroot.org/T/#mabff98d436895c18f177c4016792ec215f645bbf>
>
> I’d prefer not to mention the limitation (as it’s an
> rstudio-specific modification to DESCRIPTION files) and instead
> work on supporting this extension to the DESCRIPTION file. I
> already have some WIP to address this.
Just to clarify, you are referring to the fact that the ‘--recursive’
option won’t work, not the fact that the ‘hg’ binary needs to be in
$PATH, right? In that case I will send a new reroll removing the
following sentence:
--8<---------------cut here---------------start------------->8---
+One limitation of this is that dependencies that are also hosted on Git
+or Mercurial repositories cannot be imported.
--8<---------------cut here---------------end--------------->8---
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2021-12-19 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 11:03 [bug#51509] [PATCH] doc: Mention Hg support for 'guix import cran' and some caveats Xinglu Chen
2021-11-27 9:17 ` Ricardo Wurmus
2021-12-19 9:04 ` Xinglu Chen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yrlothx.fsf@disroot.org \
--to=public@yoctocell.xyz \
--cc=51509@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.