Github messages for voidlinux
 help / color / mirror / Atom feed
From: gnif <gnif@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: LookingGlass-B1
Date: Fri, 29 Apr 2022 15:20:08 +0200	[thread overview]
Message-ID: <20220429132008.12kOaajgNY416iQv5DPNaBcp78l3p-5F_q1PsoxlTOA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13393@inbox.vuxu.org>

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

New comment by gnif on void-packages repository

https://github.com/void-linux/void-packages/pull/13393#issuecomment-1113302677

Comment:
> > It's still Beta, it's not a final release. Please do not package this project.
> 
> You don't want distros to package your project? That is surprising... It would get more people using it - and it isn't something you'd use by accident.

Of-course we do eventually. At the moment we do not as you have to keep the Windows app and the client app versions in sync as the protocol they use to communicate is still in flux. Each time a distro has packaged our application we get inundated with support requests because of miss-matched versions.

Until LG reaches version 1.0 when we set the protocol and feature set in stone, LG is not ready for packaging.

  parent reply	other threads:[~2022-04-29 13:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 15:09 [PR PATCH] " voidlinux-github
2019-07-28 15:58 ` [PR PATCH] [Updated] " voidlinux-github
2019-07-28 15:58 ` voidlinux-github
2019-07-28 16:21 ` voidlinux-github
2019-07-28 16:21 ` voidlinux-github
2019-07-28 16:22 ` voidlinux-github
2019-07-28 16:22 ` voidlinux-github
2019-07-29 19:00 ` voidlinux-github
2020-11-01  2:01 ` ericonr
2020-11-01  2:01 ` ericonr
2022-01-05 19:18 ` ericonr
2022-01-05 23:41 ` dm17
2022-04-15  2:12 ` github-actions
2022-04-29  2:13 ` [PR PATCH] [Closed]: " github-actions
2022-04-29 12:31 ` dm17
2022-04-29 13:00 ` gnif
2022-04-29 13:04 ` dm17
2022-04-29 13:20 ` gnif [this message]
2022-04-29 13:27 ` dm17

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=20220429132008.12kOaajgNY416iQv5DPNaBcp78l3p-5F_q1PsoxlTOA@z \
    --to=gnif@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).