all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: interesting thread
Date: Wed, 24 May 2017 18:17:19 +0200	[thread overview]
Message-ID: <878tlmqlf4.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDyTqSuLNgiyqp0sH337ueyZXEa0qmH37=NhQEECv0VQag@mail.gmail.com> (catonano@gmail.com's message of "Wed, 24 May 2017 17:57:07 +0200")

Catonano writes:

> no comments ?

I saw this message, had a quick look and a frown...

> I was so enthsiast of aving discovered this

Can you summarize what's to get enthousiastic about?

>     https://lists.w3.org/Archives/Public/public-lod/2017May/0005.html
>    
>     they published the metadata about the WHOLE collection of packaged in npm !!

Having looked into npm and worked on the guix npm importer, I found that
even the some of the most trivial packages cannot be built from source.
Cyclic dependencies in the build systems.

So after having tried to get npm into GuixSD, I'm at the point of giving
up on npm and am planning to migrate away from it.

I can hardly imagine...but does this report in any way hint that some
packages can be built from source and how to do that?

Greetings,
janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

  reply	other threads:[~2017-05-24 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 17:16 interesting thread Catonano
2017-05-24 15:57 ` Catonano
2017-05-24 16:17   ` Jan Nieuwenhuizen [this message]
2017-05-24 19:26     ` Catonano
2017-05-24 20:16   ` ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tlmqlf4.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=catonano@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.