all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: HFS+ write support (packaging hfsprogs?)
Date: Wed, 03 Apr 2019 00:32:47 -0700	[thread overview]
Message-ID: <87ef6j35nk.fsf@gmail.com> (raw)
In-Reply-To: <87pnqf4cjr.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (Pierre Neidhardt's message of "Mon, 25 Mar 2019 08:51:20 +0100")

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

Hi Pierre,

Pierre Neidhardt <mail@ambrevar.xyz> writes:

> I have this external drive formatted in HFS+ (Apple's filesystem).
> I'd like to write to it.
>
> It seems that I'd need the hfsprogs package (to be confirmed).
> It's under APSL license.
>
> [...]
>
> Thoughts?

The APSL v2 (but not v1, apparently) is a free software license:

https://www.gnu.org/licenses/license-list.en.html#apsl2
https://www.gnu.org/philosophy/apsl.html

So, as long as hfsprogs is available under the APSL v2 and it does not
contain any thing that might go against the FSDG (e.g., "A free system
distribution must not steer users towards obtaining any nonfree
information for practical use, or encourage them to do so."), it's
probably OK to include in Guix.

For reference, the FSDG can be found here:

https://www.gnu.org/distros/free-system-distribution-guidelines.html

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-04-03  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25  7:51 HFS+ write support (packaging hfsprogs?) Pierre Neidhardt
2019-04-03  7:32 ` Chris Marusich [this message]
2019-04-03  8:06   ` Pierre Neidhardt
2019-04-04 16:56     ` Pierre Neidhardt

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=87ef6j35nk.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.