Github messages for voidlinux
 help / color / mirror / Atom feed
From: Thomashighbaugh <Thomashighbaugh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: AppImageLauncher
Date: Fri, 12 Nov 2021 10:06:41 +0100	[thread overview]
Message-ID: <20211112090641.UHzMASfuXHYZFnr5HMAdljwaNjafA7iFsIA5tTDL-8o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26702@inbox.vuxu.org>

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

New comment by Thomashighbaugh on void-packages repository

https://github.com/void-linux/void-packages/issues/26702#issuecomment-966938428

Comment:
I get the controversy potential because systemd is even something the original package used to achieve its functionality and because different people will approach cmake and ninja with different opinions, solutions and want their platform to discuss why they do as they do whenever possible as is the nature of the solitary work it is to embark on the Linux journey at all (and that hardheadedness is a thing with Linux factionalism where controversy ensues where its not necessary, helpful or even about anything but an excuse for people to enumerate their feelings on a subject that in their personal life they probably know few people that would ever care to hear them discuss these things for its an unusual itch that this sort of thing is even scratching most have no notion of) but can't actually see why this would be something to incite a conflagration considering the patches here are reasonable approaches to overcoming the systemd dependency that so many others do and changes to the build process that to me, at least, are reasonable and instructive even. But its Linux and passions combine with absurd egoism in patterns the envy of the greatest dramas put to stage.  

Even if its not added to `void-packages` @m4rcu5 please consider making a repo to make this something other's could easily add into their own void-packages repos locally as ibhagwan did with his fork of picom [which you can see here](https://github.com/ibhagwan/picom-ibhagwan-template) as I think this would be appreciated by many and be helpful while providing everyone a workable solution no one needs to cry foul about. 

Awesome work, thanks a lot and keep up the `good stuff`  and sorry to probe this comment train rather late, I just happened to be looking for this exact solution and am grateful these are not patches falling on me to do, thought I might chime in a bit while poking at a community tendency in my ruminative way. 

  parent reply	other threads:[~2021-11-12  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 19:48 [ISSUE] " cwross
2021-02-04 15:05 ` m4rcu5
2021-03-24  2:45 ` JJGadgets
2021-03-24 13:38 ` m4rcu5
2021-03-25  1:16 ` JJGadgets
2021-11-12  9:06 ` Thomashighbaugh [this message]
2022-02-22 18:07 [ISSUE] " distefam
2022-02-22 20:56 ` notthewave

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=20211112090641.UHzMASfuXHYZFnr5HMAdljwaNjafA7iFsIA5tTDL-8o@z \
    --to=thomashighbaugh@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).