Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Add Write from Stylus Labs
Date: Sat, 05 Sep 2020 02:59:07 +0200	[thread overview]
Message-ID: <20200905005907.iqGyMLhhfdPSB7SRn8DPmJkVwOQ0DCeyMMjQcGdvL54@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24555@inbox.vuxu.org>

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

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/24555#issuecomment-687500607

Comment:
On 2020-09-04 13:39:43-0700, cat-marin <notifications@github.com> wrote:
> @cat-marin commented on this pull request.
> 
> 
> 
> > @@ -0,0 +1,32 @@
> +# Template file for 'write-styluslabs'
> +pkgname=write-styluslabs
> +version=3.0.0
> +revision=1
> +archs="x86_64"
> +wrksrc="Write"
> +depends="SDL2"
> +short_desc="Word processor for handwriting"
> +maintainer="Cat Marin <me@jmarin.xyz>"
> +license="custom:Proprietary"
> +homepage="http://www.styluslabs.com/"
> +distfiles="http://www.styluslabs.com/write/write-latest.tar.gz"
> 
> > They provides versioned tarball, they just don't show you, here is
> > the link for 3.0.0 http://www.styluslabs.com/write/write300.tar.gz
> 
> Yep! Saw that in their response to me email. However they still
> don't have a license available, which as I understand is necessary
> in order to proceed.

The EULA is available at http://www.styluslabs.com/write/eula.docx
Either ship the docx file, or use docx2txt to convert to plain text
file


  parent reply	other threads:[~2020-09-05  0:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 19:58 [PR PATCH] " cat-marin
2020-08-30 21:01 ` [PR PATCH] [Updated] " cat-marin
2020-08-31  1:34 ` fosslinux
2020-08-31  2:05 ` cat-marin
2020-08-31  2:50 ` fosslinux
2020-08-31  3:28 ` [PR PATCH] [Updated] " cat-marin
2020-08-31  3:29 ` cat-marin
2020-08-31  3:58 ` [PR REVIEW] " fosslinux
2020-08-31  3:58 ` fosslinux
2020-08-31  4:23 ` [PR PATCH] [Updated] " cat-marin
2020-08-31  4:26 ` cat-marin
2020-08-31  4:27 ` cat-marin
2020-08-31  4:29 ` [PR PATCH] [Updated] " cat-marin
2020-08-31  6:15 ` fosslinux
2020-08-31  6:23 ` cat-marin
2020-08-31  6:24 ` fosslinux
2020-09-02 17:00 ` ahesford
2020-09-02 23:37 ` ahesford
2020-09-02 23:56 ` [PR REVIEW] " ahesford
2020-09-02 23:56 ` ahesford
2020-09-03 19:49 ` cat-marin
2020-09-03 19:52 ` cat-marin
2020-09-03 20:01 ` ericonr
2020-09-03 20:01 ` ericonr
2020-09-03 20:11 ` cat-marin
2020-09-03 20:12 ` [PR PATCH] [Closed]: " cat-marin
2020-09-03 20:12 ` cat-marin
2020-09-04  0:23 ` [PR REVIEW] " sgn
2020-09-04  0:25 ` sgn
2020-09-04 20:39 ` cat-marin
2020-09-05  0:18 ` fosslinux
2020-09-05  0:59 ` sgn [this message]
2020-09-05  4:36 ` cat-marin

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=20200905005907.iqGyMLhhfdPSB7SRn8DPmJkVwOQ0DCeyMMjQcGdvL54@z \
    --to=sgn@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).