public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [pre-GLEP] Split distfile mirror directory structure
Date: Tue, 30 Jan 2018 14:27:23 +1300	[thread overview]
Message-ID: <20180130142723.1e9b0d46@katipo2.lan> (raw)
In-Reply-To: <4e7d9732-be7a-56f0-a88f-12559cba2400@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 872 bytes --]

On Sat, 27 Jan 2018 13:24:44 -0500
Michael Orlitzky <mjo@gentoo.org> wrote:

> Fetch instructions for app-cat/pkg:
>  *
>  * Please download file1 from:
>  * wherever file1 can be found
>  * and move it to $DISTDIR/subdir1
>  *
>  * Please download file2 from
>  * wherever file2 can be found
>  * and move it to $DISTDIR/subdir2
>  *
>  * ...
>  *
>  * Please download fileN from
>  * wherever fileN can be found
>  * and move it to $DISTDIR/subdirN

Or ...: 

Please download:

  src_url1/filename1.tar.gz
  src_url2/filename2.tar.gz
  src_url3/filename3.tar.gz

And install them to your $DISTDIR with

  edistadd ./filename1.tar.gz ./filename2.tar.gz ./filename3.tar.gz

An extra perk is edistadd could also ensure the permissions are correct
for portage to read the file afterwards, which is a bit of an annoyance
sometimes as it is.

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

  parent reply	other threads:[~2018-01-30  1:27 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 23:24 [gentoo-dev] [pre-GLEP] Split distfile mirror directory structure Michał Górny
2018-01-27  1:48 ` Michael Orlitzky
2018-01-27  2:44   ` R0b0t1
2018-01-27  8:30   ` Michał Górny
2018-01-27 11:36     ` Roy Bamford
2018-01-27 11:41       ` Michał Górny
2018-01-27 16:42         ` Gordon Pettey
2018-01-27 16:48           ` Michael Orlitzky
2018-01-27 19:01             ` Gordon Pettey
2018-01-27 20:16               ` Michael Orlitzky
2018-01-30  1:21         ` Kent Fredric
2018-01-30  2:53           ` Robin H. Johnson
2018-01-30  7:25           ` Michał Górny
2018-01-30 19:46             ` Kent Fredric
2018-01-27 16:47     ` Michael Orlitzky
2018-01-27 18:14       ` Michał Górny
2018-01-27 18:24         ` Michael Orlitzky
2018-01-27 19:47           ` Michał Górny
2018-01-27 20:30             ` Michael Orlitzky
2018-01-30  1:27           ` Kent Fredric [this message]
2018-01-30  7:17             ` Ulrich Mueller
2018-01-28  7:01 ` Jason Zaman
2018-01-28  9:10   ` Michał Górny
2018-01-29  7:33   ` Robin H. Johnson
2018-01-28 10:14 ` Ulrich Mueller
2018-01-28 10:16   ` Michał Górny
2018-01-28 10:22     ` Ulrich Mueller
2018-01-28 10:40       ` Michał Górny
2018-01-28 13:03         ` Ulrich Mueller
2018-01-30  1:41           ` Kent Fredric
2018-01-30  7:11             ` Ulrich Mueller
2018-01-28 20:43 ` Andrew Barchuk
2018-01-28 21:17   ` Gordon Pettey
2018-01-28 22:00     ` Andrew Barchuk
2018-01-28 22:13       ` Gordon Pettey
2018-01-28 22:14       ` Zac Medico
2018-01-28 22:46         ` Andrew Barchuk
2018-01-29  5:36   ` Michał Górny
2018-01-29  9:22     ` Andrew Barchuk
2018-01-29 19:37 ` [gentoo-dev] [pre-GLEP] Split distfile mirror directory structure (draft v2) Michał Górny
2018-01-29 20:00   ` Robin H. Johnson
2018-01-29 21:09     ` Michał Górny
2018-01-29 20:26   ` R0b0t1
2018-01-29 20:55     ` Alec Warner

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=20180130142723.1e9b0d46@katipo2.lan \
    --to=kentnl@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