unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Michael Zappa <me@michzappa.com>, 51048@debbugs.gnu.org
Subject: bug#51048: No license in crate - guix import
Date: Wed, 06 Oct 2021 08:20:58 +0200	[thread overview]
Message-ID: <7580ba1ecf974cfc08391d8b62e1fbbc796350bb.camel@telenet.be> (raw)
In-Reply-To: <87h7dvnlxv.fsf@michzappa.com>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

Michael Zappa schreef op di 05-10-2021 om 18:31 [-0400]:
> Hello all,
> I have been playing around with the 'guix import' tools to
> see how easily I can get some package definitions. In the process of
> trying to package https://github.com/Spotifyd/spotifyd with 'guix import
> crate spotifyd -r' I found that one of the nested dependencies,
> libpulse-sys@0.0.0 did not work with the automatic importer because it
> does not have a license in its crate
> https://crates.io/crates/libpulse-sys/0.0.0.
> 
> Obviously it would be ideal to get whoever is using this out-of-date
> library in their package to update their dependencies so this is
> entirely avoided, but short of that has there ever been discussion on
> how to handle 'license-less' packages? I haven't seen any in my short
> time lurking on this list. It seems to be a rigid requirement for the
> crate importer.

I don't now if there has been a discussion,
but other importers (at least the minetest importer) set the license
field to #f if no license information was unavailable.

Modifying <crate-version> such that 'license' is set to #f if it has 
'null' as value in the JSON might be sufficient I think?

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-10-06  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 22:31 bug#51048: No license in crate - guix import Michael Zappa
2021-10-06  6:20 ` Maxime Devos [this message]
2021-10-07  8:52   ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=7580ba1ecf974cfc08391d8b62e1fbbc796350bb.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=51048@debbugs.gnu.org \
    --cc=me@michzappa.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).