[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Using (recursive #t) in (origin git-reference)
From: |
( |
Subject: |
Re: Using (recursive #t) in (origin git-reference) |
Date: |
Tue, 20 Jun 2023 20:50:39 +0100 |
John Kehayias <john.kehayias@protonmail.com> writes:
> This happens enough I feel like it should be explicitly mentioned as a
> potential
> "gotcha" in the manual, even if one can gleam it from understanding package
> definitions and hashes, if it isn't already. Or maybe a little "tips" section
> on
> packaging (or in the cookbook) with something like this and related ones like
> idiosyncrasies/conventions in certain language ecosystems. We all accumulate a
> lot of institutional knowledge as we do and pass it along, but better to have
> it
> properly referenced.
Sounds like an idea. I definitely think it should go in the manual,
though, as it'll be far more visible there. (I, personally, have never
read the cookbook in all that much detail...)
-- (