Hey Guix,
Is there any particular reason why our current ncurses packages builds without
versioned symbols? Upstream specifies only default versions (i.e. via @@), no
forced ones, so IIUC that should make the library drop-in replaceable for
everything we have so far. Am I missing something?
On 2022-03-17, Matt wrote:
> On Thu, 17 Mar 2022 21:04:13 -0400 Vagrant Cascadian
> wrote
> > The description and synopsis fixes are generally pretty easy, so might
> > make for good first steps for someone wanting to get familiar with the
> > process of contributing without having
--- Original Message ---
On Sunday, April 10th, 2022 at 8:19 PM, Justin Veilleux
wrote:
> 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
I have a ROCKPro64 (Hexa-Core Rockchip RK3399, 4GB) which I plan to use
for guix development too. I was already able to get PureOS in a chroot.
Tobias
Attila Lendvai schreef op ma 11-04-2022 om 06:49 [+]:
> these names are pretty much independent from each other
> (modulo some conventions), and this is an issue for the importers.
> more specifically the go importer, that currently needs scheme variable
> names to refer to the identified
Attila Lendvai schreef op ma 11-04-2022 om 06:49 [+]:
> if someone wants to use guix as a platform for reproducible builds
> of go projects (independent of guix revisions), then a package
> definitions is needed that refers to specific versions of its
> dependencies.
>
> currently it's not
As mentionned on GNUnet mailing list [1][], gnurl is affected by security
issues.
[1]: https://lists.gnu.org/archive/html/gnunet-developers/2022-04/msg00021.html
It might not affect GNUnet, but I tried to update the package in Guix anyway,
and…
I failed! ^_^'
```console
$ ./pre-inst-env guix
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
