From: Rovanion Luckey <rovanion.luckey@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org
Subject: Re: [RFC] Package of Nomacs
Date: Thu, 31 Dec 2020 16:37:43 +0100 [thread overview]
Message-ID: <CAAaf0CCnorD+5jpuyGUg-23Njo9hUX+k0es7ZcwbMpR8N-pAew@mail.gmail.com> (raw)
In-Reply-To: <424245f9f30e2418942a8eec27019864294550cd.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
Hi Leo and thank you for your comments.
The nomacs package should probably go to gnu/packages/image-
> viewers.scm.
>
Yup.
> Use git-fetch instead and don't recurse into submodules. You will
> likely encounter some errors, because it doesn't seem as though nomacs
> expects you to have its inputs properly packages. *sigh*
>
Hmm, this one I'm not sure I understand the reasoning behind. I think I
read in some packaging guidelines that url-fetch was preferred if possible.
> Instead of adding the path to the source directory, try `(cd
> "ImageLounge")` in a phase after 'unpack.
>
I'm told that cd is an unbound variable when I try that :/
#:phases (modify-phases %standard-phases
(add-after 'unpack 'cd-to-source-dir
(lambda _ (call-with-output-string (cd
"ImageLounge")))))
Try to sort them alphabetically, also don't put too much effort into
> making the tails align.
>
Check.
> One thing that's missing is the plugins that are developed in a
> > separate git repository [0] and not included in the source tarballs
> > of the main repository [1]. Ideas on how to make them available in
> > the `plugins` directory during build time are welcome.
> A trick that's often used in Guix is
> (inputs
> `(("extra-source-package"
> ,(origin ...)))
> [other inputs])
> You can then (copy-recursively (assoc-ref inputs "extra-source-
> package") destination) in a phase between 'unpack and 'configure.
>
Thank you! And thank you for the rest of the comments too.
Happy new year!
[-- Attachment #2: Type: text/html, Size: 2645 bytes --]
next prev parent reply other threads:[~2020-12-31 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 18:32 [RFC] Package of Nomacs Leo Prikler
2020-12-31 15:37 ` Rovanion Luckey [this message]
2020-12-31 16:12 ` Leo Prikler
2021-01-01 22:02 ` Rovanion Luckey
2021-01-02 14:43 ` Rovanion Luckey
2021-01-02 15:42 ` Leo Prikler
2021-01-03 1:01 ` Rovanion Luckey
2021-01-07 16:58 ` zimoun
-- strict thread matches above, loose matches on Subject: below --
2020-12-29 23:06 Rovanion Luckey
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=CAAaf0CCnorD+5jpuyGUg-23Njo9hUX+k0es7ZcwbMpR8N-pAew@mail.gmail.com \
--to=rovanion.luckey@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).