public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eddie Chapman <eddie@ehuk.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Current unavoidable use of xz utils in Gentoo
Date: Sat, 13 Apr 2024 08:10:22 +0100	[thread overview]
Message-ID: <3de8c850-6fed-46e6-a52f-70695dad9eac@ehuk.net> (raw)
In-Reply-To: <c5a2b579-8c3e-45c7-b859-b41a675d15d5@gentoo.org>

Joonas Niilola wrote:
> Hey,
> 
> I'll admit I didn't read everything, but I just want to point out you
> may not have to edit ebuilds at all. If xz-utils is package.provided 
> portage should ignore the dependency without you removing the dep from an
> ebuild. Then you can utilize /etc/portage/patches to apply any patches and
> finally try using EXTRA_ECONF and MYMESONARGS to override configure
> options via package.env.
> 
> -- juippis

Hi Joonas,

The local ebuilds in the guide were not created because of the xz-utils 
dep. If you search through ebuilds in the tree there are hundreds of 
packages that specify xz-utils as a hard dep, so yes, as you say, 
package.provided takes care of all of then.

No, the ebuilds were needed for various customisations to build 
arguments. However, the dev-libs/libxmlb ebuild is no longer needed as, 
since I wrote the guide, libxmlb 0.3.17, which makes liblzma.so.5 dep 
optional, is now in Gentoo, thanks whoever added that :-)

You might be able to dispense with the need for the separate 
net-mail/dovecot ebuild by using EXTRA_ECONF, as you say. However, 
AFAICS local dev-lang/python ebuilds are unavoidable, unfortunately, 
you'll see why if you look at the diffs for them in my guide. It would 
be wonderful if dev-lang/python made its liblzma dep optional. It would 
be a simple change to the ebuild. However, I suspect the developers 
might feel that *not* depending on liblzma.so.5 is unsupported because 
it results in Gemato failing due to lack of support in core python for 
liblzma. The only way around that issue I can see is for Gemato to 
instead use /usr/bin/xz like the rest of Portage does. If that were to 
happen then dev-lang/python could be modified to respect -lzma and I 
can't see that anything significant in Gentoo would miss it. Then if 
there are any dev-python packages that need liblzma in core python 
either presently or in future (I've not encountered any yet) then of 
course they would just need a hard dependency on dev-lang/python with 
lzma USE flag set.

I now have many Gentoo systems running without xz-utils installed (using 
my wrapper script from the guide) and I've not had a single issue 
anywhere, everything working perfectly, so I'm delighted that it has 
been possible :-)

Eddie


  parent reply	other threads:[~2024-04-13  7:10 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30  3:07 [gentoo-dev] Current unavoidable use of xz utils in Gentoo Eddie Chapman
2024-03-30  3:43 ` orbea
2024-03-30  7:06   ` Dale
2024-03-30 10:47     ` [gentoo-dev] " Duncan
2024-03-30 11:32     ` [gentoo-dev] " Rich Freeman
2024-03-30 14:57       ` Eddie Chapman
2024-03-30 15:02         ` Michał Górny
2024-03-30 15:17           ` Eddie Chapman
2024-03-30 15:29             ` Michał Górny
2024-03-30 15:59               ` Eddie Chapman
2024-03-30 16:07             ` Dale
2024-03-30 17:13             ` Re[2]: " Stefan Schmiedl
2024-03-30 17:36               ` Eddie Chapman
2024-03-31  1:41                 ` Thomas Gall
2024-03-30 23:49             ` Eddie Chapman
2024-03-31  1:36             ` Eli Schwartz
2024-03-30 15:23           ` orbea
2024-03-30 15:14         ` Rich Freeman
2024-03-30 17:19           ` Eddie Chapman
2024-03-31  1:25 ` Sam James
2024-03-31  1:33 ` Eli Schwartz
2024-03-31 11:13   ` Eddie Chapman
2024-03-31 11:59     ` Matt Jolly
2024-04-01  7:57       ` Eddie Chapman
2024-04-01 14:50         ` Eli Schwartz
2024-04-02  8:43           ` Eddie Chapman
2024-04-02 19:46             ` Eli Schwartz
2024-04-02 20:19               ` Eddie Chapman
2024-04-01 14:55         ` Michał Górny
2024-04-02  9:02           ` Eddie Chapman
2024-04-01 15:14     ` Kenton Groombridge
2024-04-01 15:40       ` orbea
2024-04-01 16:01         ` Kenton Groombridge
2024-04-01 16:21           ` orbea
2024-04-01 18:51             ` Kévin GASPARD DE RENEFORT
2024-04-01 20:07               ` James Le Cuirot
2024-04-02  6:32                 ` Joonas Niilola
2024-03-31 11:32   ` stefan11111
2024-04-01 14:56 ` Azamat Hackimov
2024-04-02 19:32   ` Eddie Chapman
2024-04-03 11:47     ` [gentoo-dev] " Duncan
2024-04-03 12:14       ` Sam James
2024-04-03 15:30         ` [gentoo-dev] " Eddie Chapman
2024-04-03 16:40           ` Michael Orlitzky
2024-04-04  3:20             ` [gentoo-dev] " Duncan
2024-04-04  3:49           ` [gentoo-dev] " Eli Schwartz
2024-04-04  8:32             ` Sam James
2024-04-04  8:34               ` Kévin GASPARD DE RENEFORT
2024-04-04 14:38               ` Eddie Chapman
2024-04-04 14:24             ` Eddie Chapman
2024-04-06 11:57               ` Eddie Chapman
2024-04-06 12:15                 ` Ulrich Mueller
2024-04-06 12:34                 ` Roy Bamford
2024-04-06 14:04                 ` Fabian Groffen
2024-04-07  6:44                   ` Eddie Chapman
2024-04-06 16:15                 ` Sam James
2024-04-07 11:24                   ` Eddie Chapman
2024-04-11  5:21                 ` Joonas Niilola
2024-04-12  7:18                   ` [gentoo-dev] " Duncan
2024-04-13  7:10                   ` Eddie Chapman [this message]
2024-04-03 12:22       ` Kévin GASPARD DE RENEFORT
2024-04-03 12:26         ` Kévin GASPARD DE RENEFORT
2024-04-04  1:41         ` Duncan

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=3de8c850-6fed-46e6-a52f-70695dad9eac@ehuk.net \
    --to=eddie@ehuk.net \
    --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