From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] built_with_use removal
Date: Sun, 24 Jan 2010 18:51:00 +0200 [thread overview]
Message-ID: <4B5C7A74.80107@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
I looked at what kind of a difference cvs up made to built_with_use usage.
betelgeuse@pena /usr/portage $ grep --include "*.ebuild" built_with_use
-r . | wc -l
690
cvs up
betelgeuse@pena /usr/portage $ grep --include "*.ebuild" built_with_use
-r . | wc -l
708
There should be no legitimate reason for the number to go up so please
whenever bumping ebuilds, remove the usage of built_with_use.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2010-01-24 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 16:51 Petteri Räty [this message]
2010-01-24 18:09 ` [gentoo-dev] built_with_use removal "Paweł Hajdan, Jr."
2010-01-24 20:16 ` Petteri Räty
2010-01-24 20:12 ` [gentoo-dev] Re: [gentoo-dev-announce] " Diego Elio “Flameeyes” Pettenò
2010-01-24 22:23 ` Petteri Räty
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=4B5C7A74.80107@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-dev-announce@lists.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