From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Upcoming repoman check will fail on large files in the tree
Date: Fri, 30 Jul 2004 12:15:49 +0900 [thread overview]
Message-ID: <20040730031549.GA25543@ols-dell.iic.hokudai.ac.jp> (raw)
In-Reply-To: <410955B0.1030301@gossamer-threads.com>
maillog: 29/07/2004-12:53:20(-0700): Jason Rhinelander types
> Mike Frysinger wrote:
> >On Thursday 29 July 2004 05:52 am, Brian Harring wrote:
> >
> >>Policy states files over 20k are not to be commited- I'll be committing
> >>the logic to enforce this shortly- files over 20k will be viewed by
> >>repoman as a failed check.
> >
> >just so you guys know, the answer is NOT to compress them and add them
> >back into the tree
>
> There seem to be rather a lot of those already:
>
> find /usr/portage/*-* -regex '.*\.\(tgz\|tbz2\|gz\|bz2\)'
>
> Is there a specific policy about not having compressed file in the tree?
> If I'm not mistaken, a gz'ed or bz2'ed file in portage is sort of
> pointless, since the rsync enables compression. Maybe repoman could
> complain about .gz, .bz2, .tgz, or .tbz2 files in the tree as well?
What about not allowing binary files at all?
--
\ Georgi Georgiev \ No line available at 300 baud. \
/ chutz@gg3.net / /
\ +81(90)6266-1163 \ \
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-30 3:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 9:52 [gentoo-dev] Upcoming repoman check will fail on large files in the tree Brian Harring
2004-07-29 14:15 ` Mike Frysinger
2004-07-29 19:53 ` Jason Rhinelander
2004-07-30 3:15 ` Georgi Georgiev [this message]
2004-07-30 3:20 ` Brian Harring
2004-07-30 3:22 ` Ciaran McCreesh
2004-07-30 4:07 ` Ciaran McCreesh
2004-07-30 7:00 ` Robin H. Johnson
2004-07-30 7:43 ` Ciaran McCreesh
2004-08-25 6:56 ` Tavis Ormandy
2004-08-25 14:40 ` Mike Frysinger
2004-08-25 17:19 ` Robert Moss
2004-08-26 14:34 ` Eldad Zack
-- strict thread matches above, loose matches on Subject: below --
2004-08-25 13:08 Peter Cech
2004-08-25 15:31 ` Andrew Cooks
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=20040730031549.GA25543@ols-dell.iic.hokudai.ac.jp \
--to=chutz@gg3.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