unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
* Install new package in current generation?
@ 2018-05-23  0:44 Jone
  2018-05-23  5:43 ` Ricardo Wurmus
  0 siblings, 1 reply; 7+ messages in thread
From: Jone @ 2018-05-23  0:44 UTC (permalink / raw)
  To: help-guix

Now:

guix package -i PACKAGE  # -> creating new generation
guix package -d          # remove all generations, except current
guix gc

- not so good: first creating new generation, and next delete all
others (I absolutely do not need a rollback).

Maybe some other way?

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Install new package in current generation?
  2018-05-23  0:44 Install new package in current generation? Jone
@ 2018-05-23  5:43 ` Ricardo Wurmus
  2018-05-23  7:33   ` Pierre Neidhardt
  0 siblings, 1 reply; 7+ messages in thread
From: Ricardo Wurmus @ 2018-05-23  5:43 UTC (permalink / raw)
  To: Jone; +Cc: help-guix


Jone <yeger9@gmail.com> writes:

> guix package -i PACKAGE  # -> creating new generation
> guix package -d          # remove all generations, except current
> guix gc
>
> - not so good: first creating new generation, and next delete all
> others (I absolutely do not need a rollback).

There is no other way.  Guix always generates a new generation of your
profile.

--
Ricardo

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Install new package in current generation?
  2018-05-23  5:43 ` Ricardo Wurmus
@ 2018-05-23  7:33   ` Pierre Neidhardt
  2018-05-23 14:35     ` Jone
  2018-05-23 15:41     ` Ludovic Courtès
  0 siblings, 2 replies; 7+ messages in thread
From: Pierre Neidhardt @ 2018-05-23  7:33 UTC (permalink / raw)
  To: Ricardo Wurmus; +Cc: help-guix

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]


>> guix package -i PACKAGE  # -> creating new generation
>> guix package -d          # remove all generations, except current
>> guix gc

Technically you don't need to always call `guix gc`.

Also note that generations are generally lightweight, especially for
simple operations like installing a single package.

-- 
Pierre Neidhardt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Install new package in current generation?
  2018-05-23 14:35     ` Jone
@ 2018-05-23 11:40       ` Ricardo Wurmus
  2018-05-23 15:30         ` Jone
  0 siblings, 1 reply; 7+ messages in thread
From: Ricardo Wurmus @ 2018-05-23 11:40 UTC (permalink / raw)
  To: Jone; +Cc: help-guix


Jone <yeger9@gmail.com> writes:

>> Also note that generations are generally lightweight
>
> It's right. But I have another problem with different generations:
> I build and install xfce4-cpugraph-plugin
>
> /gnu/store/qf0khvz9vj5lj4k9sfjxqlbs0kl8ssr3-xfce4-cpugraph-plugin-1.0.5/
> ├── lib
> │ └── xfce4
> │     └── panel
> │         └── plugins
> │             ├── libcpugraph.la
> │             └── libcpugraph.so
> ...
>
> of course xfce-panel does not see libcpugraph.so
>
> /gnu/store/rp40p839f65bzkkzrgcx7jbxb0c38nx4-xfce4-panel-4.12.0/
> ├── bin
> ...
> │ └── xfce4
> │     └── panel
> │         ├── migrate
> │         ├── plugins
> │         │ ├── libactions.la
> │         │ ├── libactions.so
> │         │ ├── libapplicationsmenu.la
> │         │ ├── libapplicationsmenu.so
> │         │ ├── libclock.la
> │         │ ├── libclock.so
> │         │ ├── libdirectorymenu.la
> │         │ ├── libdirectorymenu.so
> │         │ ├── liblauncher.la
> │         │ ├── liblauncher.so
> │         │ ├── libpager.la
> │         │ ├── libpager.so
> │         │ ├── libseparator.la
> │         │ ├── libseparator.so
> │         │ ├── libshowdesktop.la
> │         │ ├── libshowdesktop.so
> │         │ ├── libsystray.la
> │         │ ├── libsystray.so
> │         │ ├── libtasklist.la
> │         │ ├── libtasklist.so
> │         │ ├── libwindowmenu.la
> │         │ └── libwindowmenu.so
> │         ├── wrapper-1.0
> │         └── wrapper-2.0
> ...
>
> Problem! Probably I should to modify the "xfce" package itself, but it's
> not so easy for me.

Garbage collection won’t make a difference here.

According to the definition of the “xfce” and “xfce4-panel” packages,
plugins are searched for on directories listed in the environment
variable “X_XFCE4_LIB_DIRS”.  Try setting that to the directory
containing “xfce4-cpugraph-plugin” before Xfce is started.

--
Ricardo

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Install new package in current generation?
  2018-05-23  7:33   ` Pierre Neidhardt
@ 2018-05-23 14:35     ` Jone
  2018-05-23 11:40       ` Ricardo Wurmus
  2018-05-23 15:41     ` Ludovic Courtès
  1 sibling, 1 reply; 7+ messages in thread
From: Jone @ 2018-05-23 14:35 UTC (permalink / raw)
  To: Pierre Neidhardt; +Cc: help-guix

> Also note that generations are generally lightweight

It's right. But I have another problem with different generations:
I build and install xfce4-cpugraph-plugin

/gnu/store/qf0khvz9vj5lj4k9sfjxqlbs0kl8ssr3-xfce4-cpugraph-plugin-1.0.5/
├── lib
│   └── xfce4
│       └── panel
│           └── plugins
│               ├── libcpugraph.la
│               └── libcpugraph.so
...

of course xfce-panel does not see libcpugraph.so

/gnu/store/rp40p839f65bzkkzrgcx7jbxb0c38nx4-xfce4-panel-4.12.0/
├── bin
...
│   └── xfce4
│       └── panel
│           ├── migrate
│           ├── plugins
│           │   ├── libactions.la
│           │   ├── libactions.so
│           │   ├── libapplicationsmenu.la
│           │   ├── libapplicationsmenu.so
│           │   ├── libclock.la
│           │   ├── libclock.so
│           │   ├── libdirectorymenu.la
│           │   ├── libdirectorymenu.so
│           │   ├── liblauncher.la
│           │   ├── liblauncher.so
│           │   ├── libpager.la
│           │   ├── libpager.so
│           │   ├── libseparator.la
│           │   ├── libseparator.so
│           │   ├── libshowdesktop.la
│           │   ├── libshowdesktop.so
│           │   ├── libsystray.la
│           │   ├── libsystray.so
│           │   ├── libtasklist.la
│           │   ├── libtasklist.so
│           │   ├── libwindowmenu.la
│           │   └── libwindowmenu.so
│           ├── wrapper-1.0
│           └── wrapper-2.0
...

Problem! Probably I should to modify the "xfce" package itself, but it's
not so easy for me.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Install new package in current generation?
  2018-05-23 11:40       ` Ricardo Wurmus
@ 2018-05-23 15:30         ` Jone
  0 siblings, 0 replies; 7+ messages in thread
From: Jone @ 2018-05-23 15:30 UTC (permalink / raw)
  To: Ricardo Wurmus; +Cc: help-guix

> listed in the environment variable “X_XFCE4_LIB_DIRS”

It works! Thanks.

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Install new package in current generation?
  2018-05-23  7:33   ` Pierre Neidhardt
  2018-05-23 14:35     ` Jone
@ 2018-05-23 15:41     ` Ludovic Courtès
  1 sibling, 0 replies; 7+ messages in thread
From: Ludovic Courtès @ 2018-05-23 15:41 UTC (permalink / raw)
  To: Pierre Neidhardt; +Cc: help-guix

Pierre Neidhardt <ambrevar@gmail.com> skribis:

>>> guix package -i PACKAGE  # -> creating new generation
>>> guix package -d          # remove all generations, except current
>>> guix gc
>
> Technically you don't need to always call `guix gc`.

Indeed, just run it when you need more disk space.  On some machines I
have “guix gc -F100G” run periodically, which ensures that 100G of disk
is available.

Ludo’.

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2018-05-24  7:28 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-23  0:44 Install new package in current generation? Jone
2018-05-23  5:43 ` Ricardo Wurmus
2018-05-23  7:33   ` Pierre Neidhardt
2018-05-23 14:35     ` Jone
2018-05-23 11:40       ` Ricardo Wurmus
2018-05-23 15:30         ` Jone
2018-05-23 15:41     ` Ludovic Courtès

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).