unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Packaging Arcan
Date: Mon, 26 Nov 2018 16:49:40 +0100	[thread overview]
Message-ID: <cucefb7kfe3.fsf@lprndn.info> (raw)
In-Reply-To: <f248b556-9218-48b1-7b01-09588a04fa8a@riseup.net> (swedebugia's message of "Fri, 23 Nov 2018 19:09:55 +0100")

Hello,

Thank you for the help.
I decided to package appls on their own as they are not part of Arcan
itself and can be written by anyone.
My plan, if I understood correctly, is to copy appls file to
'%out/share/arcan/appl' as the folder already exists in Arcan package so
that everything is "merged" in a single folder in the user profile. 
I first thought that setting a search-path in the Arcan package would
then let the user deal with the rest. (Are search-paths honored
automatically under GuixSD?)

But after installing Arcan, 'guix package --search-paths'
doesn't output anything related to the variable I set. I don't have any
hint telling me to set it myself during installation.
Am I misunderstanding something about search-paths?

Here is the piece of code I added to the Arcan definition:
    (search-paths
    '((search-path-specification 
       (variable "ARCAN_APPLBASEPATH")
       (files '("share/arcan/appl")))))
       
Last question here, in a specific appl (Durden), there a little shell
script which set some variables/folders and start arcan. Is it ok to put
it in "%outbin"?

Lprndn

  reply	other threads:[~2018-11-26 14:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 12:14 Packaging Arcan L p R n d n
2018-11-23 11:40 ` Pierre Neidhardt
2018-11-23 12:54   ` L p R n d n
2018-11-23 12:16     ` Pierre Neidhardt
2018-11-26 15:59   ` L p R n d n
2018-11-23 12:32 ` L p R n d n
2018-11-23 18:09   ` swedebugia
2018-11-26 15:49     ` L p R n d n [this message]
2018-11-23 17:12 ` Thorsten Wilms

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=cucefb7kfe3.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.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 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).