From: Shyam Saran <syamsaran12345@gmail.com>
To: 48398@debbugs.gnu.org
Subject: bug#48398: many packages become nonfunctional if not install in fixed profile like ~/.guix-profile
Date: Thu, 13 May 2021 19:56:11 +0530 [thread overview]
Message-ID: <CABVJY8o6o+uBM8+q4S=PM0j_iCCqxrtuDz=ZbLUv18QhohKyqA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
many packages become nonfunctional if not install in fixed profiles (e.g.
~/.guix-profile)
These are two instances
1. blueman
2. font-conf so most of font like font-lohit will not be available
I had noticed that fixed profiles have become part of many
packages/services definition
which could be the reason that many of these packages/services become
dependent on
these fixed profiles.
It can be checked with
$ ag --scheme '.guix-profile'
$ grep -r '.guix-profile'
in code
Also
We provides necessary services through putting environment variables in
each profiles
PROFILE_PATH/etc/profile
like for pidgin/purple
PURPLE_PLUGIN_PATH
for libraries
LIBRARY_PATH
As suggestion
We could first provide augment all variables with guix specific prefix e.g.
GUIX_PEV_...
(PVS profile environment variables.)
So these all variables will become
GUIX_PEV_PURPLE_PLUGIN_PATH
GUIX_PEV_LIBRARY_PATH
then we could or could not (left to user) to set them
PURPLE_PLUGIN_PATH=$GUIX_PEV_PURPLE_PLUGIN_PATH
LIBRARY_PATH=$GUIX_PEV_LIBRARY_PATH
So with prefixed env vars, in first look one will know it is coming from
guix related profiles.
maybe it will also help in removing dependencies on fixed profiles.
/syam
[-- Attachment #2: Type: text/html, Size: 1978 bytes --]
next reply other threads:[~2021-05-13 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 14:26 Shyam Saran [this message]
2021-05-13 21:55 ` bug#48398: many packages become nonfunctional if not install in fixed profile like ~/.guix-profile Leo Prikler
2021-05-18 8:14 ` Shyam Saran
2021-05-18 8:35 ` Leo Prikler
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='CABVJY8o6o+uBM8+q4S=PM0j_iCCqxrtuDz=ZbLUv18QhohKyqA@mail.gmail.com' \
--to=syamsaran12345@gmail.com \
--cc=48398@debbugs.gnu.org \
/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).