From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC} glib-2.0 cleanup
Date: Mon, 01 Mar 2010 10:15:57 -0500 [thread overview]
Message-ID: <20100301151557.GD15391@denix.org> (raw)
In-Reply-To: <6ec4247d1002281340t76447b67hc0457bbf702d38b9@mail.gmail.com>
On Mon, Mar 01, 2010 at 08:10:31AM +1030, Graham Gower wrote:
> On 1 March 2010 06:56, Frans Meulenbroeks <fransmeulenbroeks@gmail.com> wrote:
> > 2010/2/28 Koen Kooi <k.kooi@student.utwente.nl>:
> >>
> >> But more importantly, what harm do the recipes do to you? Does it offend
> >> you that there are 26 recipes?
> >
> > Somewhat yes. Frankly I don't see a use for 26 recipes for all kind of
> > different versions, some of which are very outdated.
>
> What should offend you more is stuff like this:
>
> [grg@rak gcc]$ pwd
> /home/grg/oe/openembedded/recipes/gcc
> [grg@rak gcc]$ find . -name svn-updates.dpatch -exec ls -l {} \;
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-4.4.2/debian/svn-updates.dpatch
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-4.4.1/debian/svn-updates.dpatch
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-4.3.1/debian/svn-updates.dpatch
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-4.3.3/debian/svn-updates.dpatch
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-4.3.4/debian/svn-updates.dpatch
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-svn/debian/svn-updates.dpatch
> -rw-r--r-- 1 grg users 17668056 2009-11-15 12:59
> ./gcc-4.3.2/debian/svn-updates.dpatch
> [grg@rak gcc]$ grep svn-updates *
> [grg@rak gcc]$
So, there is 125 MB wasted right there... Thanks for the heads up! :)
--
Denys
next prev parent reply other threads:[~2010-03-01 15:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 19:39 [RFC} glib-2.0 cleanup Frans Meulenbroeks
2010-02-28 20:05 ` Koen Kooi
2010-02-28 20:26 ` Frans Meulenbroeks
2010-02-28 21:40 ` Graham Gower
2010-03-01 15:15 ` Denys Dmytriyenko [this message]
2010-03-01 15:20 ` Frans Meulenbroeks
2010-03-01 15:25 ` Marcin Juszkiewicz
2010-03-06 19:36 ` Frans Meulenbroeks
2010-02-28 21:35 ` Michael 'Mickey' Lauer
2010-03-01 7:30 ` Frans Meulenbroeks
2010-03-01 14:35 ` Koen Kooi
2010-03-01 14:43 ` Dr. Michael Lauer
2010-03-01 15:02 ` bitbake -b with BBCLASSEXTENDed recipes Was: " Martin Jansa
2010-03-15 16:48 ` bitbake -b with BBCLASSEXTENDed recipes Enrico Scholz
2010-03-16 3:23 ` Denys Dmytriyenko
2010-03-17 8:48 ` Martin Jansa
2010-03-17 10:03 ` Enrico Scholz
2010-03-01 22:11 ` [RFC} glib-2.0 cleanup Khem Raj
2010-03-01 22:30 ` Denys Dmytriyenko
2010-03-01 22:34 ` Chris Larson
2010-03-01 22:49 ` Khem Raj
2010-03-01 22:51 ` Chris Larson
2010-03-01 23:04 ` Khem Raj
2010-03-01 23:26 ` Chris Larson
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=20100301151557.GD15391@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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