From: Rich Freeman <rich0@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] (draft) final report for OpenRC soc project 2012
Date: Mon, 27 Aug 2012 08:37:17 -0400 [thread overview]
Message-ID: <CAGfcS_=UOTjgxchs5pwqwmQfTqYQv2GUBtwJPxkgeavLddPSKw@mail.gmail.com> (raw)
In-Reply-To: <503B5008.6000205@gentoo.org>
On Mon, Aug 27, 2012 at 6:46 AM, Patrick Lauer <patrick@gentoo.org> wrote:
> We already have patches to fix things thanks to Polynomial-C aka. Lars
> Wendler. See:
> http://dev.gentoo.org/~polynomial-c/udev/
>
> Now we only need to motivate our maintainers to use the openrc useflag
> to fix udev properly.
Hmm, only a 53K patch. Why not just fork the thing? Heaven forbid
maybe that might actually get everybody to agree on virtualizing it
which would seem to make everybody happy anyway.
And I'm not all that keen on having so many changes controlled by a
use flag, unless it were part of some kind of agreed-upon transition
plan like with KDE back in the move to /usr. It is like having two
different packages in one anyway.
Keep in mind that motivation in a volunteer-based project generally
does not include hitting somebody over the head until they quit. It
is also generally the case that package maintainers tend to be aligned
with upstream, since if they didn't have a strong interest in the
package they probably wouldn't be maintaining it in the first place.
If somebody submitted a 53K patch to just about any other team in
Gentoo they'd be told to take it upstream. Heck, Gentoo paid for a
patch to git and we didn't even apply our own patch until upstream
refined and merged it (though we did backport it - and I think all of
this is exactly how it should have been done).
Rich
next prev parent reply other threads:[~2012-08-27 15:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:58 [gentoo-soc] report 7.16-7.23: improving OpenRC heroxbd
2012-08-07 4:53 ` [gentoo-soc] report 7.24-8.7: " heroxbd
2012-08-07 9:16 ` Luca Barbato
2012-08-08 23:24 ` [gentoo-soc] report 8.8: " heroxbd
2012-08-09 6:05 ` Luca Barbato
2012-08-10 2:56 ` [gentoo-soc] report 8.9: " heroxbd
2012-08-10 8:51 ` Luca Barbato
2012-08-11 0:31 ` [gentoo-soc] report 8.10: " heroxbd
2012-08-11 23:50 ` [gentoo-soc] report 8.11: " heroxbd
2012-08-13 8:33 ` Luca Barbato
2012-08-15 15:14 ` [gentoo-soc] (draft) final report for OpenRC soc project 2012 heroxbd
2012-08-15 21:47 ` Luca Barbato
2012-08-16 8:38 ` heroxbd
2012-08-16 11:41 ` Rich Freeman
2012-08-17 5:39 ` heroxbd
2012-08-17 7:29 ` Luca Barbato
2012-08-17 11:56 ` Rich Freeman
2012-08-20 3:04 ` heroxbd
2012-08-20 8:16 ` Luca Barbato
2012-08-20 10:25 ` Fabian Groffen
2012-08-20 16:32 ` Luca Barbato
2012-08-20 18:25 ` Fabian Groffen
2012-08-20 10:47 ` Rich Freeman
2012-08-20 16:34 ` Luca Barbato
2012-08-20 18:12 ` Rich Freeman
2012-08-20 18:28 ` Luca Barbato
2012-08-20 16:15 ` EBo
2012-08-21 14:07 ` heroxbd
2012-08-21 15:55 ` Luca Barbato
2012-08-22 2:04 ` heroxbd
2012-08-22 7:35 ` Luca Barbato
2012-08-27 10:46 ` Patrick Lauer
2012-08-27 12:37 ` Rich Freeman [this message]
2012-08-27 13:29 ` Luca Barbato
2012-08-27 14:10 ` Rich Freeman
2012-08-27 14:35 ` Luca Barbato
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='CAGfcS_=UOTjgxchs5pwqwmQfTqYQv2GUBtwJPxkgeavLddPSKw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-soc@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