From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Can pkg_nofetch determine if a file is already downloaded?
Date: Mon, 15 Oct 2018 20:05:38 +0200 [thread overview]
Message-ID: <1539626738.1014.0.camel@gentoo.org> (raw)
In-Reply-To: <a00296e0-fb33-98b9-ff26-59fe31d0b2b5@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Mon, 2018-10-15 at 13:34 +0200, Michael Haubenwallner wrote:
> Hi,
>
> in pkg_nofetch, beyond to "direct the user to download relevant source files",
> I've found it useful to tell the user which filesystem directory to put the
> files into once downloaded.
>
> Beyond that, I've also found it useful to tell the user whether a relevant
> source file is 'already there' or 'still missing'.
>
> Since the EAPI 6 related update to pkg_* phases to not have access to DISTDIR
> (even in earlier EAPI) any more, I'm wondering if both informations are still
> available to pkg_nofetch in one or another way.
>
> Any idea?
>
> Or is my only option to reduce the information to "all these files need to be
> put in your DISTDIR", requiring the user to find out both the right DISTDIR
> and which of the listed files are still missing herself?
>
How would you know whether the file in DISTDIR is correct and complete?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-10-15 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 11:34 [gentoo-dev] Can pkg_nofetch determine if a file is already downloaded? Michael Haubenwallner
2018-10-15 15:57 ` Ulrich Mueller
2018-10-15 18:05 ` Michał Górny [this message]
2018-10-17 16:03 ` [gentoo-dev] " Michael Haubenwallner
2018-10-17 16:14 ` Michał Górny
2018-10-18 13:34 ` Kent Fredric
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=1539626738.1014.0.camel@gentoo.org \
--to=mgorny@gentoo.org \
--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