unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: raingloom <raingloom@riseup.net>,
	Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: non-input dependencies Was: guile-dbi from guix not working
Date: Mon, 30 May 2022 12:01:56 +0530	[thread overview]
Message-ID: <871qwbedk3.fsf@systemreboot.net> (raw)
In-Reply-To: <20220529172314.5fabbe36@riseup.net>


> IMHO as a first step we should just add this information to the package
> descriptions. Simple, backwards compatible, doesn't restrict us, etc.
> Eg.: for emacs-geiser, just add a line that says: "To use it with a
> given Scheme dialect, install emacs-geiser-<scheme-dialect> in the
> same environment."
> Bam, no more confusion over why a package isn't doing anything.

I agree with this fix. And, it seemed very easy. So, I started working
on it. But, when I try to change the guile-dbi package description,
`guix lint' complains that since guile-dbi is a GNU package, we should
prefer to keep the upstream description. Now, it seems like we should
change the upstream guile-dbi description to change the Guix package
description. Feels a little bureaucratic to me.


      reply	other threads:[~2022-05-30  6:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 11:26 guile-dbi from guix not working Zelphir Kaltstahl
2022-05-07 18:44 ` Luis Felipe
2022-05-08 12:33   ` Zelphir Kaltstahl
2022-05-25 19:18 ` Arun Isaac
2022-05-28 16:37   ` Zelphir Kaltstahl
2022-05-29  7:57     ` Arun Isaac
2022-05-29  8:58       ` non-input dependencies Was: " raingloom
2022-05-29 14:42         ` Zelphir Kaltstahl
2022-05-29 15:23           ` raingloom
2022-05-30  6:31             ` Arun Isaac [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=871qwbedk3.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=help-guix@gnu.org \
    --cc=raingloom@riseup.net \
    --cc=zelphirkaltstahl@posteo.de \
    /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).