public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markus Walter <lists@jonglieren-jena.de>
To: gentoo-portage-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-portage-dev] Normaliser function for distfiles
Date: Tue, 17 May 2022 16:50:31 +0200	[thread overview]
Message-ID: <86r14srz60.wl-lists@jonglieren-jena.de> (raw)
In-Reply-To: <fff527dc8365c8a0b4be204584bb2338ee4ad205.camel@gentoo.org>

On Tue, 17 May 2022 16:35:11 +0200,
Michał Górny wrote:
> This would require a new EAPI.  We don't really want more Portage-
> specific hacks that are going to break for everyone not using Portage or
> the very specific Portage version.
> 
> I'm not saying that it's not doable but I'm not convinced the added
> complexity is really worth the effort, especially given that this looks
> like a very special corner case.  In the end, fixing Melpa is the right
> thing to do.
> 
> For a start, you'd have to ensure that the "normalizer script" (or its
> dependencies, if you put it in the repo) is available at the time of
> fetching.  This pretty much goes back to the problem of "fetch
> dependencies", and requires a major design change in Portage that
> reduces separation between fetching and installing that we have now.
> I mean, right now Portage pretty much assumes that you can do
> a `--fetchonly` with no extra packages necessary.
> 
> The "normalizer" wouldn't be trivial either.  In the end, we're talking
> about getting 100% consistent results on all platforms, over
> a reasonably long timeframe.

Oh, what a chain of complexity. Yeah, I'll go try fixing melpa first.


         Markus

-- 
For instance, on the planet Earth, man had always assumed that he was more
intelligent than dolphins because he had achieved so much---the wheel, New
York, wars and so on---while all the dolphins had ever done was muck about
in the water having a good time. But conversely, the dolphins had always
believed that they were far more intelligent than man---for precisely the
same reasons. (Douglas Adams, The Hitchhikers Guide to the Galaxy.)


      reply	other threads:[~2022-05-17 14:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 17:37 [gentoo-portage-dev] Normaliser function for distfiles Markus Walter
2022-05-17  3:21 ` Zac Medico
2022-05-17 11:27   ` Markus Walter
2022-05-17  3:39 ` Robin H. Johnson
2022-05-17 11:31   ` Markus Walter
2022-05-17 12:14 ` Rich Freeman
2022-05-17 12:32   ` Markus Walter
2022-05-17 13:22     ` Rich Freeman
2022-05-17 14:35 ` Michał Górny
2022-05-17 14:50   ` Markus Walter [this message]

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=86r14srz60.wl-lists@jonglieren-jena.de \
    --to=lists@jonglieren-jena.de \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=mgorny@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