Re: Cyclic npm dependencies

2018-11-24 Thread Jelle Licht
Op za 24 nov. 2018 om 16:38 schreef Pjotr Prins : > On Sat, Nov 24, 2018 at 03:41:35PM +, Jelle Licht wrote: > >Hey swedebugia, > >I will still send a more elaborate reply to the general npm-importer > >thread later this week, but we can assume that generally these > >

Re: Octave & QtOctave

2018-11-24 Thread ng0
names for packages are (mostly) random, although in some cases following classiifcations (see python-*, r-*, ...). The Qt part of Octave is a separate package because making it just an output would still pull in Qt and the size difference is huge. Alex Vong transcribed 856 bytes: > Hello, > >

Re: Cyclic npm dependencies

2018-11-24 Thread Pjotr Prins
On Sat, Nov 24, 2018 at 03:41:35PM +, Jelle Licht wrote: >Hey swedebugia, >I will still send a more elaborate reply to the general npm-importer >thread later this week, but we can assume that generally these >recursive dependencies can be untangled by looking at the different >

Re: Cyclic npm dependencies

2018-11-24 Thread Jelle Licht
Hey swedebugia, I will still send a more elaborate reply to the general npm-importer thread later this week, but we can assume that generally these recursive dependencies can be untangled by looking at the different versions of the dependencies. So in your example, I imagine an input chain like:

Cyclic npm dependencies

2018-11-24 Thread swedebugia
Hi We need to wonder about what to do with cyclic dependencies. In the case below node-rimraf has node-glob in input and node-glob has node-rimraf in NATIVE-input. I have no idea how to solve this. Both packages are by the same author. Same problem with jasmine and jasmine-core

Re: Move Clojure and Femtolisp

2018-11-24 Thread Pierre Neidhardt
Done! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: supporting EOL ruby in Guix

2018-11-24 Thread Alex Vong
Pjotr Prins writes: > I think we can now drop the unsupported versions. I was using 1.8 > until quite recently ;). These packages can be put into channels for > those who need that. > Ok, so we can drop them for guix. But I think we should still try to fix as many CVEs as possible even if we

Re: NPM importer

2018-11-24 Thread swedebugia
On 2018-11-22 09:36, Julien Lepiller wrote: Thanks! It made me wonder if we could better approximate the set of needed dependencies by looking at package tags. I'll try to improve my script in that spirit, and share it again here. Sounds good. I would like to work on implementing a way to

Re: NPM importer

2018-11-24 Thread swedebugia
Hi On 2018-11-20 08:50, Julien Lepiller wrote: snip I'll push what I have to a wip-branch latter today. The reason why I develop out-of-tree is because I can always rebase my patches. I don't see it in guix yet. Could you push it? I corrected a bug in node-build-system and added

Re: Octave & QtOctave

2018-11-24 Thread Alex Vong
Hello, Brett Gilio writes: > Hey all, > > Happy guix birthday! > > Quick question, why is the octave package split up into two different > public definitions, rather than just having the QtOctave-GUI being a > "gui" output, like it is for transmissionBT and some others? > I would also want to

Re: Getting ‘core-updates’ merged

2018-11-24 Thread Danny Milosavljevic
Hi Ludo, On Fri, 23 Nov 2018 14:52:42 +0100 l...@gnu.org (Ludovic Courtès) wrote: > -- >