From: "Petteri Räty" <betelgeuse@gentoo.org>
To: bugday@gentoo.org, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Suggestion for next bugday: Mass use deps migration
Date: Fri, 20 Feb 2009 18:55:35 +0200 [thread overview]
Message-ID: <499EE087.1030802@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
I suggest that we dedicate the next bugday in March to migrating as many
built_with_use calls to use dependencies as possible. Actively
maintained packages should have mostly been migrated by now and in
general it's better for the user experience to get rid of all those
built_with_use calls instead of waiting for the unmaintained/slacking
parts of the tree to get migrated.
Suggestions/objections?
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2009-02-20 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:55 Petteri Räty [this message]
2009-02-22 21:34 ` [gentoo-dev] Suggestion for next bugday: Mass use deps migration Carsten Lohrke
2009-02-22 21:43 ` Tomáš Chvátal
2009-02-22 23:41 ` Carsten Lohrke
2009-02-22 21:58 ` Petteri Räty
2009-02-22 23:35 ` Carsten Lohrke
2009-03-07 14:14 ` 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=499EE087.1030802@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=bugday@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