Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Ionen Wolkens
On Tue, Jun 04, 2024 at 02:37:56PM -0400, Ionen Wolkens wrote: > On Tue, Jun 04, 2024 at 07:45:39PM +0200, Ulrich Mueller wrote: > > In any case, the above size considerations aren't important. My main > > point is that the code is getting way too complicated for the simple > > task of printing a f

Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Ulrich Mueller
> On Tue, 04 Jun 2024, Florian Schmaus wrote: > And yes, "docompress -x README.gentoo" would make the code mch > simpler. Go for it then. Apparently it is the lesser evil. signature.asc Description: PGP signature

Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Ionen Wolkens
On Tue, Jun 04, 2024 at 07:45:39PM +0200, Ulrich Mueller wrote: > In any case, the above size considerations aren't important. My main > point is that the code is getting way too complicated for the simple > task of printing a few lines in pkg_postinst. Have to say that this is mostly how I feel a

Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Eli Schwartz
On 6/4/24 2:28 PM, Florian Schmaus wrote: > And yes, "docompress -x README.gentoo" would make the code mch > simpler. And, as additional benefit, would help us get rid of storing > the whole content of the readme in a environment variable (which is what > readme.gentoo-r1.elcass currently d

Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Florian Schmaus
On 04/06/2024 19.45, Ulrich Mueller wrote: On Tue, 04 Jun 2024, Florian Schmaus wrote: Both is fine with me. That said, many filesystem support inline data. If I am not mistaken, then its even enabled by default for xfs (which we recommend in the handbook) and btrfs. Also some README.gentoo

Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Ulrich Mueller
> On Tue, 04 Jun 2024, Florian Schmaus wrote: > Both is fine with me. > That said, many filesystem support inline data. If I am not mistaken, > then its even enabled by default for xfs (which we recommend in the > handbook) and btrfs. Also some README.gentoo files become suitable for > inlini

[gentoo-dev] Last-rite app-emacs/libegit2

2024-06-04 Thread Maciej Barć
Deprecated git integration backend of "app-emacs/magit". No longer supported by upstream. Fails to compile (bug 928920). Removal on 2024-07-04. app-emacs/libegit2 -- Have a great day! ~ Maciej XGQT Barć https://wiki.gentoo.org/wiki/User:Xgqt 9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C

Re: [gentoo-dev] [PATCH 1/4] readme.gentoo-r1.eclass: display readme if content changed (or fresh install)

2024-06-04 Thread Florian Schmaus
On 02/06/2024 20.24, Ulrich Mueller wrote: Installing another file just for the sake of avoiding "docompress -x" doesn't solve the problem but makes it worse, IMHO. Rather don't compress README.gentoo then. Both is fine with me. That said, many filesystem support inline data. If I am not mista