Github messages for voidlinux
 help / color / mirror / Atom feed
From: martnnw <martnnw@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: package request : Aseprite  
Date: Thu, 10 Sep 2020 23:13:49 +0200	[thread overview]
Message-ID: <20200910211349.ZCWngB9hi4frRdoNzgMIwmYL8pmt93r8PWaz2ZyLzJE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24800@inbox.vuxu.org>

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

New comment by martnnw on void-packages repository

https://github.com/void-linux/void-packages/issues/24800#issuecomment-690735007

Comment:
> I think that it's better to package the libre fork of Aseprite directly (thus completely ditching the proprietary version).

It's OSS but not Free Software (in the FSF sense). 

Reading the EULA it seems that the only way to distribute Asprite on void is to provide a template that the user of the application needs to self compile using xbps-src (similar to discord). 
> (g) Source code.
You may only compile and modify the source code of the SOFTWARE PRODUCT for your own personal purpose or to propose a contribution to the SOFTWARE PRODUCT.


  parent reply	other threads:[~2020-09-10 21:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  5:56 [ISSUE] " siduck765
2020-09-10 10:29 ` kartikynwa
2020-09-10 11:28 ` flexibeast
2020-09-10 12:19 ` kartikynwa
2020-09-10 12:50 ` martnnw
2020-09-10 12:50 ` martnnw
2020-09-10 16:10 ` siduck765
2020-09-10 17:46 ` ericonr
2020-09-10 20:48 ` rc-05
2020-09-10 21:10 ` martnnw
2020-09-10 21:13 ` martnnw [this message]
2020-09-10 21:14 ` martnnw
2020-09-10 21:16 ` martnnw
2020-09-10 21:17 ` martnnw
2020-09-10 21:18 ` martnnw
2020-09-10 21:26 ` rc-05
2020-09-10 21:26 ` martnnw
2020-09-10 21:41 ` martnnw
2020-11-30  6:14 ` kotajacob
2021-11-24 22:19 ` notthewave
2022-01-22 13:55 ` kintrix007

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=20200910211349.ZCWngB9hi4frRdoNzgMIwmYL8pmt93r8PWaz2ZyLzJE@z \
    --to=martnnw@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).