unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Frederickson <jonathan@terracrypt.net>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: guix-devel@gnu.org
Subject: Re: Permissions error during libhandy build - looking for tips
Date: Sun, 7 Jul 2019 17:40:55 -0400	[thread overview]
Message-ID: <20190707174055.01bd6461@terracrypt.net> (raw)
In-Reply-To: <4cfe1fd1-2a97-2f43-22db-4c19f890f286@web.de>

On Sun, 7 Jul 2019 20:47:06 +0200
Jonathan Brielmaier <jonathan.brielmaier@web.de> wrote:
> It tries to install the libglade-handy.so to the glade package, which
> is forbidden. m4jn72l561mppfh12br1vcrp9x9y812p-glade-3.22.1 is a
> different package, which you can't change during the install process
> of libhandy...

Ahh, yeah, makes sense. I noticed that store path is different than
the one for the glade package in my profile, so I thought Guix might
have extended the glade package somehow... guess not.

> So there are two options from here:
> - bring meson to install libglade-handy.so to the libhandy package
> - don't intall libglade-handy.so at all

Is the former the usual method for providing libraries like this? If
I'm interpreting this correctly, meson somehow found the path to the
glade package during the build, and I'd have to figure out how and
override that to ensure libglade-handy.so ends up in the build tree for
the libhandy package?

Assuming that's the case, am I correct in thinking that Glade (the UI
editor) will then be able to find libglade-handy.so because it'll be in
my profile?
 
> 0.0.10 is out, I think we should package this version.

You're right; I started attempting this before 0.0.10 came out, but
whenever I submit the package I'll pull in the latest version.

> I would change this:
> (origin
>        (method url-fetch)
>        (uri (string-append
> "https://source.puri.sm/Librem5/libhandy/-/archive/"
>                            version
>                            "/libhandy-"
>                            version
>                            ".tar.gz"))
> 
> to an origin based on git-fetch from a tag. This is usually better in
> terms of reproducibility:
> 
> (source (origin
>               (method git-fetch)
>               (uri (git-reference
>                      (url "https://source.puri.sm/Librem5/libhandy")
>                      (commit version)))
>               (file-name (git-file-name name version))

Ah, I forgot that the parameter to "commit" could also be a tag. I'll
adjust that.

> By the way: Am I right in the assumption that you are interested in
> the Librem 5?

Yup! I saw someone having trouble installing libhandy in one of their
chatrooms, and I was thinking it might be interesting to try and get
some of their software running with Guix. (Who knows, maybe we could
run Guix System on the Librem 5 once it's out!)

  reply	other threads:[~2019-07-07 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 16:41 Permissions error during libhandy build - looking for tips Jonathan Frederickson
2019-07-07 18:47 ` Jonathan Brielmaier
2019-07-07 21:40   ` Jonathan Frederickson [this message]
2019-07-08  9:23     ` Jonathan Brielmaier
2019-07-08 15:53       ` Jonathan Brielmaier

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=20190707174055.01bd6461@terracrypt.net \
    --to=jonathan@terracrypt.net \
    --cc=guix-devel@gnu.org \
    --cc=jonathan.brielmaier@web.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.
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).