public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Files for doc building
Date: Tue, 21 May 2024 16:46:48 -0400	[thread overview]
Message-ID: <e410ec7b-2974-4d56-ae01-e7e49a2faa3b@gmail.com> (raw)
In-Reply-To: <5b30319b-37af-4212-8c9e-9107fed27a20@eurecom.fr>


[-- Attachment #1.1.1: Type: text/plain, Size: 783 bytes --]

On 5/21/24 4:10 PM, Henri Gasc wrote:
> Hello,
> 
> I am in the process of updating dev-python/mkdocs-rss-plugin (in GURU),
> and I find myself in a pinch.
> To build the documentation, there are 74 files needed. It's too much to
> add them to the SRC_URI and copy the files in src_prepare, but at the
> same time, the best compression achieved on a tar archive is 3.3M and I
> worry about putting it in a files directory.
> 
> Does anyone has an idea on how to solve this ? I would prefer not to
> create a git repo and add it from there.
> Regards,
> Henri Gasc


It is even a violation of Gentoo policy to have files larger than IIRC
20kb in files/.

This *must* be handled via SRC_URI, where to host the tarball is up to
the maintainer.

-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

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

      reply	other threads:[~2024-05-21 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 20:10 [gentoo-dev] Files for doc building Henri Gasc
2024-05-21 20:46 ` Eli Schwartz [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=e410ec7b-2974-4d56-ae01-e7e49a2faa3b@gmail.com \
    --to=eschwartz93@gmail.com \
    --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