From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: sublime suite: unrestrict
Date: Sun, 19 Jun 2022 01:34:37 +0200 [thread overview]
Message-ID: <20220618233437.rbYKQzmQ05UH-mt3CgdFAhhiZiZycCWYlIJLHZ1A_P4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37593@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
There's a merged pull request on the void-packages repository
sublime suite: unrestrict
https://github.com/void-linux/void-packages/pull/37593
Description:
- sublime-merge: unrestrict, merge template with sublime-merge-bin
- sublime-text3: unrestrict, merge template with sublime-text3-bin
- sublime-text4: unrestrict
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Sublime's [EULA](https://www.sublimehq.com/eula) was updated recently to allow for redistribution of the Linux version (emphasis mine):
> 2.b. Distribution.
> You may not distribute or sell license keys or the SOFTWARE PRODUCT to third parties. **Only the Linux version of the SOFTWARE PRODUCT may be distributed to third parties.** Distribution or sale of the SOFTWARE PRODUCT to third parties outside of this exception will result in revocation of the license.
This means these packages no longer need to be restricted, however they are still nonfree, and will stay in that repo.
The `-bin` packages have been converted to transitional dummy packages, which clutters the diff a bit.
I also added `update` files for sublime text 3/4
closes #37589
prev parent reply other threads:[~2022-06-18 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 3:39 [PR PATCH] " classabbyamp
2022-06-17 16:36 ` [PR REVIEW] " Chocimier
2022-06-17 16:36 ` Chocimier
2022-06-18 6:28 ` [PR PATCH] [Updated] " classabbyamp
2022-06-18 6:41 ` classabbyamp
2022-06-18 18:59 ` [PR REVIEW] " Chocimier
2022-06-18 18:59 ` Chocimier
2022-06-18 23:33 ` [PR PATCH] [Updated] " classabbyamp
2022-06-18 23:34 ` classabbyamp [this message]
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=20220618233437.rbYKQzmQ05UH-mt3CgdFAhhiZiZycCWYlIJLHZ1A_P4@z \
--to=classabbyamp@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).