Github messages for voidlinux
 help / color / mirror / Atom feed
From: brasb <brasb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: vscodium
Date: Fri, 08 Sep 2023 05:30:39 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45967@inbox.vuxu.org> (raw)

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

New issue by brasb on void-packages repository

https://github.com/void-linux/void-packages/issues/45967

Description:
### Package name

vscodium

### Package homepage

https://vscodium.com/

### Description

Xbps only contains Code - OSS, but we should also have VSCodium. The reason for this is that Code - OSS violates the Marketplace's [terms of service](https://cdn.vsassets.io/v/M190_20210811.1/_content/Microsoft-Visual-Studio-Marketplace-Terms-of-Use.pdf):


> Marketplace Offerings are intended for use only with In-Scope Products and Services and you may install and use Marketplace Offerings only with In-Scope Products and Services.


For this reason, VSCodium uses Open VSX instead of the Marketplace. Therefore, I think it is a good idea to include VSCodium in the repository.

### Does the requested package meet the package requirements?

System

### Is the requested package released?

No

             reply	other threads:[~2023-09-08  3:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  3:30 brasb [this message]
2023-09-08  3:35 ` classabbyamp
2023-10-24  0:40 ` Zeitsperre
2024-06-02  2:18 ` Vinfall
2024-06-02  3:16 ` sgn
2024-06-02  9:07 ` Vinfall
2024-06-14  6:51 ` [ISSUE] [CLOSED] " classabbyamp
  -- strict thread matches above, loose matches on Subject: below --
2023-02-17 16:24 [ISSUE] Package request: VSCodium carbongreat13

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45967@inbox.vuxu.org \
    --to=brasb@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).