public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ]
Date: Sat, 10 Feb 2024 19:58:30 -0500	[thread overview]
Message-ID: <7fb923b6-7bd3-4878-8195-751756fa2d14@gmail.com> (raw)
In-Reply-To: <20240210032216.6a7637ae@Akita>


[-- Attachment #1.1.1: Type: text/plain, Size: 1411 bytes --]

On 2/10/24 6:22 AM, orbea wrote:
> On Fri, 9 Feb 2024 16:56:55 -0500
> Eli Schwartz <eschwartz93@gmail.com> wrote:
>> As evidenced by the removal of libressl and eudev, this logic is
>> fallacious and wrong and not the way Gentoo is developed.
> 
> Fwiw I still use both and Gentoo removing specifically Libressl has
> only been detrimental. There is a huge amount of extra and redundant
> maintainer work when all of the fixes have to be applied over and over
> again without changes as the main Gentoo repo gets updated. Its
> relatively rare that the fixes have to be rebased or changed against
> their respective upstream, but rebasing it against Gentoo is an
> extremely common and tedious task.
> 
> Your argument is invalid and not appreciated.


Sorry, could you clarify what you mean by this?

I made a comment about the facts of reality regarding how Gentoo *is*
developed. I understand that this has posed challenges to you and makes
your work harder. Nonetheless, my statement about facts and realities is
true: Gentoo really did remove upstream tree support for both from the
::gentoo tree.

What, therefore, is "invalid" about my argument? Are you writing to the
mailing list to inform me that my understanding of reality is invalid,
and that contrary to my belief, the ::gentoo tree *does* officially
support (and package!) libressl and eudev?


-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-02-11  0:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 15:23 [gentoo-dev] special small-files USE flag without effect on dependencies: [ unicode ] Andrey Grozin
2024-02-09 15:43 ` Mike Gilbert
2024-02-09 15:54 ` Ionen Wolkens
2024-02-09 16:07   ` Michael Orlitzky
2024-02-09 16:57     ` Mike Gilbert
2024-02-09 17:17       ` Michael Orlitzky
2024-02-09 18:40         ` Mike Gilbert
2024-02-09 19:09         ` Eli Schwartz
2024-02-09 19:57           ` Michael Orlitzky
2024-02-09 21:04             ` Eli Schwartz
2024-02-09 21:25               ` Michael Orlitzky
2024-02-09 21:56                 ` Eli Schwartz
2024-02-09 22:56                   ` stefan11111
2024-02-10  0:03                     ` Matt Jolly
2024-02-10 11:48                     ` David Seifert
2024-02-10 17:26                       ` stefan11111
2024-02-11  0:58                         ` Eli Schwartz
2024-02-10 11:22                   ` orbea
2024-02-11  0:58                     ` Eli Schwartz [this message]
2024-02-10  0:04               ` Sam James
2024-02-11  0:42                 ` Eli Schwartz
2024-02-11  3:46                   ` Sam James
2024-02-11  3:56                     ` Eli Schwartz
2024-02-12  4:54                     ` Andrey Grozin
2024-02-10  0:00             ` Sam James
2024-02-09 23:52 ` Sam James

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=7fb923b6-7bd3-4878-8195-751756fa2d14@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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