Github messages for voidlinux
 help / color / mirror / Atom feed
From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lsd: update to 0.22.0 and adopt
Date: Thu, 14 Jul 2022 09:27:32 +0200	[thread overview]
Message-ID: <20220714072732.oZs7oXyIERNGAlqE9zo3k4XSMfR6n2yc9PHmSgnMtPw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37904@inbox.vuxu.org>

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

New comment by tranzystorek-io on void-packages repository

https://github.com/void-linux/void-packages/pull/37904#issuecomment-1184094358

Comment:
My only thought is that intuitively, conflicts mean that two packages overlap in functionality, beyond being usable. Making two packages with such different uses conflict based only on binary name seems wrong. They should be able to coexist peacefully.

  parent reply	other threads:[~2022-07-14  7:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 19:09 [PR PATCH] " tranzystorek-io
2022-07-06 19:15 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-06 19:29 ` tranzystorek-io
2022-07-07 20:58 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-08 14:59 ` tranzystorek-io
2022-07-12 12:01 ` tranzystorek-io
2022-07-12 23:59 ` Duncaen
2022-07-13  0:00 ` Duncaen
2022-07-13  0:00 ` Duncaen
2022-07-13  5:24 ` tranzystorek-io
2022-07-13 10:21 ` Duncaen
2022-07-13 10:23 ` Duncaen
2022-07-14  7:27 ` tranzystorek-io [this message]
2022-07-16 12:42 ` [PR PATCH] [Updated] " tranzystorek-io
2022-07-16 16:51 ` [PR PATCH] [Merged]: " paper42

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=20220714072732.oZs7oXyIERNGAlqE9zo3k4XSMfR6n2yc9PHmSgnMtPw@z \
    --to=tranzystorek-io@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).