Re: preparing the next release v0.15.0

2018-06-20 Thread Kei Kebreau
swedebugia writes: > On June 20, 2018 8:38:46 PM GMT+02:00, Kei Kebreau > wrote: > > Marius Bakke writes: > > On the NEWS side, here is what springs to mind: > > [...] > > * Packages can specify that some CVEs don't apply to them > > Around when (or what commit) was this feature introduce

Re: preparing the next release v0.15.0

2018-06-20 Thread Kei Kebreau
l...@gnu.org (Ludovic Courtès) writes: > Hello Guix! > > Thanks for all the ideas, I’ve updated NEWS accordingly. I’m sure we’re > still missing a number things (so much has happened!) so more ideas are > still welcome. :-) > > Ludo’. Hi Ludo, Looking at your changes to the log file increases

Re: preparing the next release v0.15.0

2018-06-20 Thread swedebugia
On June 20, 2018 8:38:46 PM GMT+02:00, Kei Kebreau wrote: >Marius Bakke writes: > >> On the NEWS side, here is what springs to mind: >> >[...] >> * Packages can specify that some CVEs don't apply to them > >Around when (or what commit) was this feature introduced? f4007b25476dfd97885f358d2dabb

Re: Questions regarding "Relocatable" option

2018-06-20 Thread Ludovic Courtès
Hello Yoann, YOANN P skribis: > - Could we hope to see it included in the next release ? It’s definitely gonna be there. :-) Guix is mostly rolling release, in fact. > - Could we hope to see it included by default in the binary tar.gz of this > next release to be able to use guix directly i

Re: preparing the next release v0.15.0

2018-06-20 Thread Marius Bakke
Kei Kebreau writes: > Marius Bakke writes: > >> On the NEWS side, here is what springs to mind: >> > [...] >> * Packages can specify that some CVEs don't apply to them > > Around when (or what commit) was this feature introduced? It was added in commit f4007b25476dfd97885f358d2dabbd463f6f6017,

Re: preparing the next release v0.15.0

2018-06-20 Thread Ludovic Courtès
Hello Guix! Thanks for all the ideas, I’ve updated NEWS accordingly. I’m sure we’re still missing a number things (so much has happened!) so more ideas are still welcome. :-) Ludo’.

Re: preparing the next release v0.15.0

2018-06-20 Thread Ricardo Wurmus
Hi Julien and Marius, >> On the NEWS side, here is what springs to mind: >> >> * `guix weather` now reports CI statistics >> * Guix will give hints for how to resolve common configuration errors >> * RHEL6 systems are again supported >> * Reproducibility improvements all around >> * Lots of new su

Re: preparing the next release v0.15.0

2018-06-20 Thread Nils Gillmann
Is it worth mentioning that guix pull for some time now is back to relatively decent 1GB RAM consumption? I think I had it even succeed on 512MB RAM per handwritten notes here, but I haven't had the possibility to test again on low specs.

Re: preparing the next release v0.15.0

2018-06-20 Thread Kei Kebreau
Marius Bakke writes: > On the NEWS side, here is what springs to mind: > [...] > * Packages can specify that some CVEs don't apply to them Around when (or what commit) was this feature introduced? signature.asc Description: PGP signature

Re: Bleeding edge documentation

2018-06-20 Thread Nils Gillmann
Joshua Branson transcribed 1.1K bytes: > Ricardo Wurmus writes: > > > Nils Gillmann writes: > > > >> swedebugia transcribed 1.0K bytes: > >>> Hi > >>> > >>> I would like to have a continously updated documentation for guix on the > >>> webpage in addition to the release documentation. > >>> > >

Re: Bleeding edge documentation

2018-06-20 Thread Joshua Branson
Ricardo Wurmus writes: > Nils Gillmann writes: > >> swedebugia transcribed 1.0K bytes: >>> Hi >>> >>> I would like to have a continously updated documentation for guix on the >>> webpage in addition to the release documentation. >>> >>> I'm trying to read up on guix and the guix.texi file is ha

Re: Improving the README and new user experience

2018-06-20 Thread swedebugia
On June 20, 2018 10:24:47 AM GMT+02:00, Danny Milosavljevic wrote: ... Snip >Nano has paren matching (Alt-]) and commenting out (Alt-3). It allows >you to select text with cursor keys, then shift-cursor keys. > >It might make sense to patch the nano status line to mention that, >though. > >

Re: Improving the README and new user experience

2018-06-20 Thread Dan Partelly
It is my oppinion that first you should very clearly define what you want from GuixSD a) is GuixSD to be a system which sees wide adoption , or is a system by developers for developers. b) What kind of users ? Industrial use or amateurs at home ? c) Server space, desktop space or both ? d) if s

Re: Bleeding edge documentation

2018-06-20 Thread Ricardo Wurmus
Nils Gillmann writes: > swedebugia transcribed 1.0K bytes: >> Hi >> >> I would like to have a continously updated documentation for guix on the >> webpage in addition to the release documentation. >> >> I'm trying to read up on guix and the guix.texi file is hard to handle on a >> mobile devi

Re: Bleeding edge documentation

2018-06-20 Thread Nils Gillmann
Ricardo Wurmus transcribed 888 bytes: > > Nils Gillmann writes: > > > swedebugia transcribed 1.0K bytes: > >> Hi > >> > >> I would like to have a continously updated documentation for guix on the > >> webpage in addition to the release documentation. > >> > >> I'm trying to read up on guix and

Re: Improving the README and new user experience

2018-06-20 Thread Danny Milosavljevic
>> Also the editors included in the image are crap because they lack two >> important features: 1) keeping track of the damn paranteses and 2) comment >> and uncomment region. >Yes. nano is crap. vi has paren matching, but doest keep tack of them . >Editing lispy code with tracking of parens

Re: Improving the README and new user experience

2018-06-20 Thread Pierre Neidhardt
I think this would be a great addition to Guix. I agree that for now Guix' learning curve is pretty steep. Even when coming from rather barebone / Do-It-Yourself distributions like Gentoo / Arch. I'm not quite sure yet how to improve the experience to new users. I'd need to install it several