From: Cory Visi <merlin@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Large files still in files/
Date: Sun, 6 Mar 2005 20:25:17 +0000 [thread overview]
Message-ID: <20050306202517.GA30996@toucan.gentoo.org> (raw)
In-Reply-To: <20050306131024.Q29561@leftmind.net>
On Sun, Mar 06, 2005 at 01:10:24PM -0500, Anthony de Boer wrote:
> Mark Loeser wrote:
> > There's also quite a large amount of binary files still in the tree. A
> > lot of them seem to be compressed patches. I'm not sure what should be
> > done with those, but I thought putting binary files into the tree was
> > discouraged unless absolutely necessary. Lots of 4k compressed patches
> > doesn't seem to be something absolutely necessary.
>
> Tying this to the Portage-tree collection-copyright issue, it might be a
> good idea for all third-party-sourced patches, with e-mail headers or
> other such authorship/source/copyright information still intact at the
> start (and happily skipped by the patch command), to be gzipped and put
> in distfiles, and the tree itself to be reserved for stuff written
> specifically for the Gentoo project.
>
> This does still leave large Gentoo-supplied patches in question; I'm
> uncomfortable with the idea of us getting *that* far from the upstream
> sources, though.
I kind of like this idea, however, I think it's idealistic. Patches need
to be modified very frequently. Especially when we combine multiple
patches and make them all work with USE flags.
A great deal of our patches really are written specifically work with our
ebuilds.
What is the real percentage of space usage from compressed or uncompressed
patches? How big of a problem is it?
-Cory
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-06 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 4:19 [gentoo-dev] Large files still in files/ Michael Sterrett -Mr. Bones.-
2005-03-06 5:09 ` Robin H. Johnson
2005-03-08 10:15 ` Michele Noberasco
2005-03-08 13:26 ` Michele Noberasco
2005-03-06 5:27 ` Mark Loeser
[not found] ` <20050206.052901.4667@leftmind.net>
2005-03-06 18:10 ` Anthony de Boer
2005-03-06 20:25 ` Cory Visi [this message]
2005-03-07 16:57 ` Martin Schlemmer
2005-03-07 17:38 ` Malte S. Stretz
2005-03-07 17:54 ` Aron Griffis
2005-03-07 18:05 ` Ciaran McCreesh
2005-03-07 18:59 ` Chris Gianelloni
2005-03-07 18:52 ` Chris Gianelloni
2005-03-07 18:52 ` Lance Albertson
2005-03-07 19:15 ` Chris Gianelloni
2005-03-08 7:39 ` Martin Schlemmer
2005-03-07 15:34 ` Chris Gianelloni
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=20050306202517.GA30996@toucan.gentoo.org \
--to=merlin@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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