delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2020/12/19/16:15:05

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <20201219205558.23864.qmail@stuge.se>
Date: Sat, 19 Dec 2020 20:55:58 +0000
From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Problem with Guile 2.2.4 dependency for gEDA 1.10.1.
References: <f5ab1b6f-dbf3-4be3-a43f-eb74b32b7a51 AT fastmail DOT com>
<ae7dca70-44c9-d905-498e-e7768a279af7 AT epilitimus DOT com>
<83d2a9f4-89a5-cf7b-4c94-738e14327057 AT fastmail DOT com>
<20201219061954 DOT 15874 DOT qmail AT stuge DOT se>
<dbc1ab4e-66e0-cfce-3bf4-0de3cf69514d AT fastmail DOT com>
MIME-Version: 1.0
In-Reply-To: <dbc1ab4e-66e0-cfce-3bf4-0de3cf69514d@fastmail.com>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote:
> > it's perfectly possible to install
> > different versions of most packages (in particular all relevant for 1.10.1)
> > to a new directory, where they do not interact with distribution packages.
..
> > The packages will be installed into the directory inst/ under the
> > home directory of the builder user.

> Wow! That is a good tutorial. Thanks. I will try it if the patch Roland 
> "published" will not work for some reason.

Roland's patch will be much less effort, certainly try it first!


> I already have a bare-bones "tester" user I can use for this. Also, 
> since guile 2.0 is located in the standard Slack /usr location, 
> /usr/local is virtually empty, so it should be a good candidate location 
> for the guile 2.2.x package so it doesn't interfere with the 2.0.11 
> package.

I would advise against using /usr/local as prefix for two reasons:

1. /usr/local is searched by default by many tools including pkg-config,
meaning that if you install say glib into /usr/local and later build some
package which searches for glib it may well pick up (and lock to) the
version in /usr/local instead of what your distribution manages in /usr.
At this point, you lose much of the use of your distribution.

2. The ld.so loader might also search /usr/local and in case the version
you install there is not backwards compatible with what you have in /usr
(shouldn't happen, but sometimes it does) then this creates a regression
where programs stop working.

Both these issues are mitigated by building/installing all dependencies
as a user to a user-owned prefix directory, where they will only ever
be used explicitly.


> I always build in user mode first and if that passes, then I build and
> install the package as root.

It should never be neccessary to build as root, but in this case I do
recommend going a step further and also keeping everything installed
in a user directory.


> As I told Roland, I must admit I have not tried to build 1.10.1 on my 
> system. I should have tried that first, before assuming it would not 
> build due to the dependency mis-match. I will try to get that done today.

It will not build without changes, but maybe Roland will provide
everything neccessary fairly soon - maybe give it a day or two. :)


Kind regards

//Peter

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019