Re: What’s next?

Hi, Efraim Flashner skribis: > On Mon, May 17, 2021 at 10:13:10PM +0200, Ludovic Courtès wrote: >> Hi, >> >> Efraim Flashner skribis: >> >> > package-transformations applied to the operating-system field of the >> > os-config. >> >> Ah, that’s a good one, but possibly tricky! What would it

Re: What’s next?

Some other cool thoughts: Package the PHP bits of wordpress. Then create a wordpress theme that uses either no or bootstrapable (reproducible?) javascript. Wordpress writes some really minimal simple wordpress themes that have minimal javascript that could be used as a start. I think there mi

Re: What’s next?

On Tue, 18 May 2021 10:05:05 -0400 Leo Famulari wrote: > On Mon, May 17, 2021 at 10:35:22PM -0400, Joshua Branson wrote: > > I suppose someone should fix the Hurd vulnerabilities as reported > > here: > > > > https://lists.gnu.org/archive/html/bug-hurd/2021-05/msg00079.html > > > > I don't thin

Re: What’s next?

On Mon, May 17, 2021 at 10:13:10PM +0200, Ludovic Courtès wrote: > Hi, > > Efraim Flashner skribis: > > > package-transformations applied to the operating-system field of the > > os-config. > > Ah, that’s a good one, but possibly tricky! What would it operate on? > Any package? Only those sho

Re: What’s next?

Katherine Cox-Buday writes: Ludovic Courtès writes: BTW, another thing that’d be nice it to use Guile-Netlink to provide a more capable static-networking service. Thank you for the reminder! This is blocking me from standing up a few edge-routers. Also, more focus on aarch64-linux su

Re: What’s next?

Ludovic Courtès writes: > BTW, another thing that’d be nice it to use Guile-Netlink to provide a > more capable static-networking service. Thank you for the reminder! This is blocking me from standing up a few edge-routers. Also, more focus on aarch64-linux substitutes! -- Katherine

Re: What’s next?

I've rebuilt only up to python 3, and a handful pytgon packages, not a lot more. I'm very confident for the one that enables optimisation, less so for the one that removes files (supposedly useless, like windows binaries and test files). I'm go for both options, maybe python-update is more wise

Re: What’s next?

Bonjour ! Julien Lepiller skribis: > In the short term I'd like to merge the python optimisations. We > discussed it before release and thought it might be nice to merge them > before c-u, from a separate branch. That’d be great! BTW, another thing that’d be nice it to use Guile-Netlink to pro

Re: What’s next?

Hi, Bone Baboon skribis: > 1) Make the core parts of Guix reproducible > > Many core parts of Guix are not reproducible. If more core parts of > Guix were reproducible it would benefit all Guix users. > > There are several core parts of Guix that are not reproducible > including: > > * Linux-li

Re: What’s next?

On Sat, May 15, 2021 at 02:08:50PM -0400, Julien Lepiller wrote: > In the short term I'd like to merge the python optimisations. We discussed it > before release and thought it might be nice to merge them before c-u, from a > separate branch. +1 Have you tested them at all yet? If so, and they

Re: What’s next?

Ludovic Courtès schreef op za 15-05-2021 om 19:47 [+0200]: > [...] > Here’s my wish list of things that look achievable within 4 to 6 months > (I hope to help on some of these): > > • [...] > > • Merging ‘core-updates’, perhaps with a switch to GCC 10? Perhaps > with support for “simplif

Re: What’s next?

Bone Baboon writes: > 1) Make the core parts of Guix reproducible > > Many core parts of Guix are not reproducible. If more core parts of > Guix were reproducible it would benefit all Guix users. > > There are several core parts of Guix that are not reproducible > including: > > * Linux-libre >

Re: What’s next?

Ludovic Courtès writes: > So, now that 1.3.0 is out the door, what’s next?! > What’s your wish list? What do you feel an urge to hack on? :-) There are two improvements on my Guix wish list. 1) Make the core parts of Guix reproducible ** I do not know if this fits into the 4-6 mont

Re: What’s next?

epo I manage on framagit). I'd also like to add some automation so I don't have to manually update the pot files :) Le 15 mai 2021 13:47:19 GMT-04:00, "Ludovic Courtès" a écrit : >Hello Guix! > >So, now that 1.3.0 is out the door, what’s next?! > >Here’s my wish

Re: What’s next?

On Mon, May 17, 2021 at 10:35:22PM -0400, Joshua Branson wrote: > I suppose someone should fix the Hurd vulnerabilities as reported here: > > https://lists.gnu.org/archive/html/bug-hurd/2021-05/msg00079.html > > I don't think the vulnerabilities have been disclosed yet nor has there > been a fix

Re: What’s next?

Leo Famulari writes: > On Sun, May 16, 2021 at 06:26:57PM +0200, Svante Signell wrote: >> What about Hurd? > > I think the answer will be: what about it? :) > > We always welcome Hurd-related work here in Guix. > I suppose someone should fix the Hurd vulnerabilities as reported here: https://li

Re: What’s next?

Hi Brendan, Brendan Tildesley skribis: > Since you asked I'll dump my nebulous wishes here. Sorry that I don't have > very > concrete suggestions and solutions, just things I think could be better. I > should also state that 99% of my thoughts about Guix are through the filter of > "I want to

Re: What’s next?

Hi, Efraim Flashner skribis: > package-transformations applied to the operating-system field of the > os-config. Ah, that’s a good one, but possibly tricky! What would it operate on? Any package? Only those showing up in the system profile? The former is not really possible; the latter is.

What’s next?

Since you asked I'll dump my nebulous wishes here. Sorry that I don't have very concrete suggestions and solutions, just things I think could be better. I should also state that 99% of my thoughts about Guix are through the filter of "I want to build a Guix based desktop distribution that can be i

Re: What’s next?

On Sun, May 16, 2021 at 06:26:57PM +0200, Svante Signell wrote: > What about Hurd? I think the answer will be: what about it? :) We always welcome Hurd-related work here in Guix.

Re: What’s next?

Hi, > • Completing and consolidating Disarchive support (see > ): continuously building the > Disarchive database, making sure it’s replicated or backed up by > SWH, and having a blog post or two explaining the whole endeavor > (I’m looking at y

Re: What’s next?

Hi Chris, >> - File search. >> >> (I did work on it a year ago, it's stuck, would need help from people >> familiar with Cuirass.) > > That sounds interesting. What does it mean? Would it help me figure > out which commands come from which package? Yes, and more ;) > A feature I remember b

Re: What’s next?

Finally finish my endlessh service. There's a version that works here: http://issues.guix.gnu.org/39136 But it runs as root and IS NOT containerized. P.S. Also there were some really great suggestions in the previous emails! -- Joshua Branson (joshuaBPMan in #guix) Sent from Emacs and Gnus

Re: What’s next?

On Sat, 15 May 2021 23:24:41 +0300 Efraim Flashner wrote: > package-transformations applied to the operating-system field of the > os-config. > Gosh, yes please. I keep bumping into this while debugging services. Also: * substitutes over bittorrent might be cool. * split packages more, similar

Re: What’s next?

Pierre Neidhardt writes: > Hi, > > Off the top of my head: > > - Optimize the man page database update during profile builds. > > - File search. > > (I did work on it a year ago, it's stuck, would need help from people > familiar with Cuirass.) That sounds interesting. What does it mean? Wo

Re: What’s next?

On Sat, 2021-05-15 at 19:47 +0200, Ludovic Courtès wrote: > Hello Guix! > > So, now that 1.3.0 is out the door, what’s next?! > > Here’s my wish list of things that look achievable within 4 to 6 > months > (I hope to help on some of these): What about Hurd?

Re: What’s next?

On 2021-05-15, Ludovic Courtès wrote: > So, now that 1.3.0 is out the door, what’s next?! > > Here’s my wish list of things that look achievable within 4 to 6 months > (I hope to help on some of these): • Add a "make dist" job to ci.guix.gnu.org to produce prereleas

Re: What’s next?

Ludovic Courtès schreef op za 15-05-2021 om 19:47 [+0200]: > Hello Guix! > > So, now that 1.3.0 is out the door, what’s next?! > > Here’s my wish list of things that look achievable within 4 to 6 months > (I hope to help on some of these): [...] Distributing substitutes over I

Re: What’s next?

Hi, Off the top of my head: - Optimize the man page database update during profile builds. - File search. (I did work on it a year ago, it's stuck, would need help from people familiar with Cuirass.) - A GUI. https://gitlab.com/daym/guix-gui.git seems to be a good starting point. Maxim

Re: What’s next?

Hi Ludovic, Those are all good ideas, but to be brief: +1 for core-updates & newer GCC. Some other things I'd like to see that seem achievable in a 4-6 months time frame: * Add .deb and .rpm formats for 'guix pack'. * Better Texlive importer * Easier way to debug (guix debug package) -> leaves

Re: What’s next?

On Sat, May 15, 2021 at 07:47:19PM +0200, Ludovic Courtès wrote: > Hello Guix! > > So, now that 1.3.0 is out the door, what’s next?! > > Here’s my wish list of things that look achievable within 4 to 6 months > (I hope to help on some of these): > > • Merging Guix H

What’s next?

Hello Guix! So, now that 1.3.0 is out the door, what’s next?! Here’s my wish list of things that look achievable within 4 to 6 months (I hope to help on some of these): • Merging Guix Home. • Completing and consolidating Disarchive support (see <https://issues.guix.gnu.org/47

Re: What’s next?

Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Chris Marusich writes: >> >>> Leo Famulari writes: >>> So, I use and recommend `guix pull`! >>> >>> I use it too. Statements by others in this thread that "nobody" uses it >>> or that "everyone" is using Git are mistaken. >>> >>> I

Re: What’s next?

Hello Ludovic, l...@gnu.org (Ludovic Courtès) writes: > Maxim Cournoyer skribis: > >> Hi, >> >> l...@gnu.org (Ludovic Courtès) writes: >> >>> Hi Brendan, >>> >>> Brendan Tildesley skribis: >>> One little annoyance I have is that guix takes every opportunity to update the list of subst

Re: What’s next?

Ricardo Wurmus skribis: > Ludovic Courtès writes: [...] >> Oops. Here we go: >> >> modified nix/libstore/build.cc >> @@ -2449,8 +2449,11 @@ void DerivationGoal::registerOutputs() >> Hash h2 = recursive ? hashPath(ht, actualPath).first : >> hashFile(ht, actualPath); >>

Re: What’s next?

Maxim Cournoyer skribis: > Hi, > > l...@gnu.org (Ludovic Courtès) writes: > >> Hi Brendan, >> >> Brendan Tildesley skribis: >> >>> One little annoyance I have is that guix takes every opportunity to >>> update the list of substitutes when guix build, guix package -u, etc... >>> is run, and fills

Re: What’s next?

On 05/24/2017 at 21:56 Ricardo Wurmus writes: > Catonano writes: > >> 2017-05-24 18:25 GMT+02:00 Jan Nieuwenhuizen : > […] >>> A friend of mine is having a second look at Guix (not SD yet) and one of >>> the most confusing things initially is `guix pull'. "When/how do I use >>> that," he asks...

Re: What’s next?

On 05/27/2017 at 12:13 Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Chris Marusich writes: >> >>> Leo Famulari writes: >>> So, I use and recommend `guix pull`! >>> >>> I use it too. Statements by others in this thread that "nobody" uses it >>> or that "everyone" is using Git are

Re: What’s next?

Ludovic Courtès writes: > Ricardo Wurmus skribis: > >> Ludovic Courtès writes: >> >>> Hello! >>> >>> Ricardo Wurmus skribis: >>> Here are some other annoyances: * the verbosity of reporting hash mismatches. You posted a neat little change for that some time ago, but I c

Re: What’s next?

Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> Hello! >> >> Ricardo Wurmus skribis: >> >>> Here are some other annoyances: >>> >>> * the verbosity of reporting hash mismatches. You posted a neat little >>> change for that some time ago, but I cannot find it any more. >> >> Oh right,

Re: What’s next?

Hi, l...@gnu.org (Ludovic Courtès) writes: > Hi Brendan, > > Brendan Tildesley skribis: > >> One little annoyance I have is that guix takes every opportunity to >> update the list of substitutes when guix build, guix package -u, etc... >> is run, and fills my terminal with output like: >> >> sub

Re: What’s next?

Ludovic Courtès writes: > Hello! > > Ricardo Wurmus skribis: > >> Here are some other annoyances: >> >> * the verbosity of reporting hash mismatches. You posted a neat little >> change for that some time ago, but I cannot find it any more. > > Oh right, see attached. I think you forgot to a

Re: What’s next?

Ricardo Wurmus skribis: > Chris Marusich writes: > >> Leo Famulari writes: >> >>> So, I use and recommend `guix pull`! >> >> I use it too. Statements by others in this thread that "nobody" uses it >> or that "everyone" is using Git are mistaken. >> >> I use Git when I want to hack on Guix. Ot

Re: What’s next?

Hi! Jan Nieuwenhuizen skribis: > A friend of mine is having a second look at Guix (not SD yet) and one of > the most confusing things initially is `guix pull'. "When/how do I use > that," he asks...and I can only say: I'm not using that...I think we > want this to work--or something like this,

Re: What’s next?

Hi Brendan, Brendan Tildesley skribis: > One little annoyance I have is that guix takes every opportunity to > update the list of substitutes when guix build, guix package -u, etc... > is run, and fills my terminal with output like: > > substitute: updating list of substitutes from > 'https://mi

Re: What’s next?

Hello! Ricardo Wurmus skribis: > Here are some other annoyances: > > * the verbosity of reporting hash mismatches. You posted a neat little > change for that some time ago, but I cannot find it any more. Oh right, see attached. > * texlive. I’m working on splitting the package up. (An agg

Re: What’s next?

I think we can try either using: - ISO dates: [Full year number]-[Two digit month number]-[Two digit day number]T[Two digit hour in 24-hour clock]:[Two digit minutes]:[Two digit seconds] - A numeric sufix: Like "latest.1" for the first generation, "latest.2" for the second, and so on, and "

Re: What’s next?

Chris Marusich writes: > Leo Famulari writes: > >> So, I use and recommend `guix pull`! > > I use it too. Statements by others in this thread that "nobody" uses it > or that "everyone" is using Git are mistaken. > > I use Git when I want to hack on Guix. Otherwise, I use 'guix pull'. > IMO, t

Re: What’s next?

On Thu, May 25, 2017 at 07:57:41AM -0700, Chris Marusich wrote: > I use Git when I want to hack on Guix. Otherwise, I use 'guix pull'. > IMO, the biggest problem with 'guix pull' is that there is no easy > rollback. I can live with long execution times (--fallback is fine, but > it'd be nice if s

Re: What’s next?

Leo Famulari writes: > So, I use and recommend `guix pull`! I use it too. Statements by others in this thread that "nobody" uses it or that "everyone" is using Git are mistaken. I use Git when I want to hack on Guix. Otherwise, I use 'guix pull'. IMO, the biggest problem with 'guix pull' is t

Re: What’s next?

On Wed, May 24, 2017 at 09:34:14PM +0200, Catonano wrote: > I think this is a problem. It' s unfair to newcomers and it damages Guix as > a project because it makes the learning curve steeper with not so much of a > point why. It's true, we collectively worked around some problems with `guix pull`

Re: What’s next?

On Wed, May 24, 2017 at 06:25:40PM +0200, Jan Nieuwenhuizen wrote: > A friend of mine is having a second look at Guix (not SD yet) and one of > the most confusing things initially is `guix pull'. "When/how do I use > that," he asks...and I can only say: I'm not using that...I think we > want this

Re: What’s next?

Catonano writes: > 2017-05-24 18:25 GMT+02:00 Jan Nieuwenhuizen : […] >> A friend of mine is having a second look at Guix (not SD yet) and one of >> the most confusing things initially is `guix pull'. "When/how do I use >> that," he asks...and I can only say: I'm not using that...I think we >>

Re: What’s next?

2017-05-24 18:25 GMT+02:00 Jan Nieuwenhuizen : > > > +1 > > A friend of mine is having a second look at Guix (not SD yet) and one of > the most confusing things initially is `guix pull'. "When/how do I use > that," he asks...and I can only say: I'm not using that...I think we > want this to work-

Re: What’s next?

As an average Guix user, I use `guix pull`. In fact, I avoid `git pull and the pre-inst-env stuff`. I prefer to work with GUIX_PACKAGE_PATH in order to work only with `guix package` and `guix build` if I do have the need to install or build something that I changed. -- - [[https://libreplanet.or

Re: What’s next?

Ludovic Courtès writes: > I think it’s time to think about what we want to work on next, ideally > before the next release, and ideally said release should be in a couple > of months rather than in 5 months. Here are some important items I can > think of: Great points! > • Implement channels:

Re: What’s next?

2017-05-24 15:11 GMT+02:00 Ludovic Courtès : > Hello Guix! > > I think it’s time to think about what we want to work on next, ideally > one little ting I'd love is Janneke's and Jlicht's solution to use "binary" nodejs packages That would allow me to play with some projects that depend on nodejs

Re: What’s next?

Ludovic Courtès 於 2017-05-24 23:11 寫道: > Hello Guix! > > I think it’s time to think about what we want to work on next, ideally > before the next release, and ideally said release should be in a couple > of months rather than in 5 months. Here are some important items I can > think of: [...] > I t

Re: What’s next?

Ludovic Courtès writes: > Hello Guix! > > I think it’s time to think about what we want to work on next, ideally > before the next release, and ideally said release should be in a couple > of months rather than in 5 months. Here are some important items I can > think of: […] Excellent points!

What’s next?

Hello Guix! I think it’s time to think about what we want to work on next, ideally before the next release, and ideally said release should be in a couple of months rather than in 5 months. Here are some important items I can think of: • Merge the ncurses installer (the ‘wip-installer’) branch

Re: [OSM-dev] [GNUnet-developers] [GSoC] Guix + GNUnet: what’s next

Hi Paul! Thank you for your instant reply! On Thu, Jul 02, 2015 at 03:56:57PM -0700, Paul Norman wrote: > On 7/2/2015 2:58 PM, Daniel Golle wrote: > >This sounds very useful eg. for Planet.osm distribution. > >http://wiki.openstreetmap.org/wiki/Planet.osm > >It's already available via BitTorrent

Re: [OSM-dev] [GNUnet-developers] [GSoC] Guix + GNUnet: what’s next

On 7/2/2015 2:58 PM, Daniel Golle wrote: This sounds very useful eg. for Planet.osm distribution. http://wiki.openstreetmap.org/wiki/Planet.osm It's already available via BitTorrent http://www.mantlik.cz/tracker/torrent_functions.php but the regions are very large and thus the files are too... In

Re: [GNUnet-developers] [GSoC] Guix + GNUnet: what’s next

Hi! Following the discussion about using GNUnet for software package distribution I started thinking about what kind of data *read access* traces matter to people's privacy. Map data bumped into my mind, because it's obvious that where one zooms down and the places one searches for tell alot about

Re: [GSoC] Guix + GNUnet: what’s next

(Sorry, I had misspelled the GNUnet mailing list address.) Rémi Birot-Delrue skribis: > Ludovic Courtès writes: > >> I’m not completely clear on how search for substitutes will work, >> though. Currently, when the user wants to build /gnu/store/xyz, ‘guix >> substitute’ simply fetches http://hy

Re: [GSoC] Guix + GNUnet: what’s next

Ludovic Courtès writes: > I’m not completely clear on how search for substitutes will work, > though. Currently, when the user wants to build /gnu/store/xyz, ‘guix > substitute’ simply fetches http://hydra.gnu.org/xyz.narinfo. How will > that work with GNUnet? Are we going to look up their /gn

Re: [GSoC] Guix + GNUnet: what’s next

Hi Rémi, Thanks for the update! So I can see two milestones now, as we discussed before: 1. Create a variant of ‘guix publish’ that publishes over GNUnet’s file sharing (FS) service, using the neat bindings that you wrote. For that you can literally copy guix/scripts/publish.scm as

[GSoC] Guix + GNUnet: what’s next

Hello Guix! Here’s a little update. The current binary package distribution (through HTTP) is based on two components: a substituer (that retrieves packages) and a publisher. The current plan is to start with adapting the publisher for GNUnet before attacking the substituer; this work will be star