Hello guix,
I have a workflow recommendation for tracking cases where we have to
work around bugs in packages we can't upgrade for a long time:
1. create a bug report for the buggy package. (Let's call this the primary bug)
2. when making a modification to work around the bug create another
bug r
Hello all,
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> n...@n0.is skribis:
>
>> names for packages are (mostly) random, although in some
>> cases following classiifcations (see python-*, r-*, ...).
>
> That randomness is very limited in practice, if I may. :-)
>
> https://gnu.org/softw
Hi
There are some crazy naming going on in the node-community. How do we
deal with this?
Note: there is another package called "babel-core" so just
stripping/replacing the weird characters won't work well.
Any ideas?
Look this example:
https://github.com/babel/babel/blob/master/packages/b
Hi people
I asked on a couple of popular packages to get a list of what devdeps
were actually needed to build the package.
Here is an example of a response:
Out of 36 devdeps only 4 are builddeps and another 2 are testdeps.
I use answers like these to populate my blacklist which now has about
Il giorno mar 27 nov 2018 alle ore 21:58 swedebugia
ha scritto:
> Hi
>
> There are some crazy naming going on in the node-community. How do we
> deal with this?
>
> Note: there is another package called "babel-core" so just
> stripping/replacing the weird characters won't work well.
>
> Any ideas
Hi Pierre,
guix-comm...@gnu.org writes:
> ambrevar pushed a commit to branch master
> in repository guix.
>
> commit 1c7372a5aadea84165376a4b8e2664b67a663c56
> Author: Pierre Neidhardt
> Date: Mon Nov 26 14:51:40 2018 +0100
>
> gnu: clang-from-llvm: Clean up share/clang folder.
>
>
Hi Nicolas,
guix-comm...@gnu.org writes:
> ngz pushed a commit to branch master
> in repository guix.
>
> commit 8b5e2e94afdef6430583c3a0ef02fe2d7fcc16d1
> Author: Nicolas Goaziou
> Date: Sun Nov 25 01:14:28 2018 +0100
>
> gnu: Add rclone.
>
> * gnu/packages/sync.scm (rclone): New
