unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: 宋文武 <iyzsong@envs.net>
To: Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Newbie user: Feedback on custom package definition
Date: Wed, 01 Mar 2023 09:12:28 +0800	[thread overview]
Message-ID: <87ilflz343.fsf@envs.net> (raw)
In-Reply-To: <CAGxMbPZEpgzbT4PMU3xVtFJuQ1MtnLSRK2JmZ8DfKAJ0W46gDQ@mail.gmail.com> (Rodrigo Morales's message of "Tue, 28 Feb 2023 17:06:29 -0500")

Rodrigo Morales <moralesrodrigo1100@gmail.com> writes:

> [...]
>   |      #:builder
>   |      #~(begin
>   |          (use-modules (guix build utils))
>   |          (chdir (assoc-ref %build-inputs "source"))
>   |          (install-file "org-recoll.el"
>   |                        (string-append
>   |                         #$output
>   |                         "/.config/emacs/libs")))))
>   |    (synopsis "My synopsis")
>   |    (description "My description")
>   |    (home-page "https://example.org/")
>   |    (license gpl3+)))
> [...]
>
> 3 The questions
> ===============
>
>   + What changes would you do to improve the definition of the package
>     that I wrote?

I would update the synopsis, description, and switch from
trivial-build-system to emacs-build-system, and send a patch to
guix-patches.


>   + Do you manage your Emacs packages with GUIX? Could you briefly
>     describe your workflow or point me to references/documentation?

Yes, I just:

1. install emacs packages (emacs, emacs-use-package, emacs-magit, etc.)
by 'guix package -i' or 'guix package -m'.

2. setup them usually in ~/.emacs.init with '(use-package ...)'.

Packages installed by guix are available to emacs like package-install
thanks to 'guix-emacs-autoload-apckages'.


  reply	other threads:[~2023-03-01  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 22:06 Newbie user: Feedback on custom package definition Rodrigo Morales
2023-03-01  1:12 ` 宋文武 [this message]
2023-03-02 15:10 ` Gary Johnson
2023-03-02 18:54   ` Vagrant Cascadian
2023-03-02 19:57     ` (
2023-03-07 13:41       ` Simon Tournier

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=87ilflz343.fsf@envs.net \
    --to=iyzsong@envs.net \
    --cc=help-guix@gnu.org \
    --cc=moralesrodrigo1100@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.
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).