From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: portablemc-3.1.1
Date: Thu, 20 Oct 2022 09:13:41 +0200 [thread overview]
Message-ID: <20221020071341.vAMz3VDDWjzYkk-GFgT31j7bCRQbVmvfhdM_1jM-K-0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40049@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/40049#issuecomment-1285050110
Comment:
@classabbyamp Indeed, I was wondering the same thing too. There is https://github.com/mindstorm38/portablemc/blob/master/src/workspace.py which is mainly "intended for development" but maybe we could re-use it somehow as per https://github.com/mindstorm38/portablemc#setup-environment.
I'm mainly wondering how the version upgrades would work with the addon sub-packages then, PyPI cannot be used as a source as it's all just minified versions of the source for the specific addon.
next prev parent reply other threads:[~2022-10-20 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 21:43 [PR PATCH] Portablemc JamiKettunen
2022-10-20 0:34 ` New package: portablemc-3.1.1 classabbyamp
2022-10-20 7:10 ` JamiKettunen
2022-10-20 7:13 ` JamiKettunen [this message]
2022-10-20 7:14 ` JamiKettunen
2022-10-20 7:39 ` classabbyamp
2022-10-20 13:50 ` icp1994
2022-10-22 14:35 ` [PR PATCH] [Updated] " JamiKettunen
2022-10-22 14:39 ` JamiKettunen
2022-10-22 14:39 ` JamiKettunen
2022-10-23 2:12 ` JamiKettunen
2022-11-04 0:08 ` JamiKettunen
2022-11-10 15:19 ` [PR PATCH] [Updated] " JamiKettunen
2022-12-04 14:38 ` New package: portablemc-3.2.0 JamiKettunen
2023-03-05 2:09 ` github-actions
2023-03-20 1:58 ` [PR PATCH] [Closed]: " github-actions
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=20221020071341.vAMz3VDDWjzYkk-GFgT31j7bCRQbVmvfhdM_1jM-K-0@z \
--to=jamikettunen@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).