here's an example of what i would add to the wiki, because i think all other
options are worse (but correct me if i'm wrong!):
open a page about highlevel design goals/issues, and then open an entry for the
problem that packages have two names in two namespaces: the scheme
module/variable names
Hi,
Am Sonntag, dem 10.04.2022 um 22:40 +0200 schrieb Ludovic Courtès:
> Hallo!
>
> Liliana Marie Prikler skribis:
>
> > given that Shepherd 0.9.0 adds support for systemd-style socket
> > activation and Emacs supports that (if linked against systemd!) I
> > wanted to try it out. Here's my "ge
Hi guix-devel.
For my os.scm, I want to create a service which encapsulates the process
of adding channels to the global channels file, adding substitute urls
to the daemon and also adding authorized keys to the daemon. With the
service extension system, I was able to do the first thing by ext
Hello,
I think it makes sense, looking at the number of impacted packages and from
my experience working
in go, even if the contract is the same, sometimes it does break on minor.
One more thing, should I do it in two patches like this?
1. Add go 1.18 inheriting from 1.17, allowing people to use
Ludovic Courtès writes:
> This comes from here:
>
> https://issues.guix.gnu.org/52808#20
>
> That is, symlink-manager no longer prepends “.” to file names given to
> ‘home-files-service-type’.
>
> Does that correspond to what you observed?
A work-around that someone on IRC discovered
Hi,
Brian Cully skribis:
> Feng Shu writes:
>>> Cleaning up symlinks from previous home at
>>> /gnu/store/m70cycn4wkhqmk85pkh8jxspbnw35sw8-home.
>>>
>>> guix home: error: rmdir: No such file or directory
>>
>> yestoday have no this problem, today I guix pull and move
>> home-files-service-type
Hi,
Pier-Hugues Pellerin skribis:
> I am trying to update Go to 1.18, I do have a *working* patch that defines
> a package that inherits from 1.17 and that adjusts the inputs.
Nice!
> However, I have a few questions:
>
> 1. Is inheriting the way to do that? The package's build system appears t
Hallo!
Liliana Marie Prikler skribis:
> given that Shepherd 0.9.0 adds support for systemd-style socket
> activation and Emacs supports that (if linked against systemd!) I
> wanted to try it out. Here's my "generic" recipe for constructing
> an Emacs service:
>
> (define* (emacs #:key (name 'se
Hi,
(Stripping Cc: list.)
Brian Cully skribis:
> Liliana Marie Prikler writes:
>
>> Am Mittwoch, dem 06.04.2022 um 23:25 +0200 schrieb Ludovic Courtès:
>>> ** Log file of unprivileged ‘shepherd’ is now under $XDG_DATA_DIR
>> Should that not be $XDG_STATE_DIR?
>
> I believe it should be
Hi Hartmut,
Hartmut Goebel skribis:
> So this is a more general discussion: Would it be better — also in
> regard to detecting new versions — to use the projects source-repo or
> the package manager's repo.
I guess it depends on how the repository is managed. It’s not uncommon
for PyPI and Ru
Hi,
Maxim Cournoyer skribis:
[...]
>>> Changing all pre-existing packages, maybe. But doing this for new
>>> packages (reducing review effort) and perhaps when a package is updated
>>> (for purity) should be feasible I think? Then gradually things would
>>> improve and eventually(TM) doing th
11 matches
Mail list logo
