From: Alistair Bush <ali_bush@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keyword policy for non standard things
Date: Wed, 22 Oct 2008 22:54:39 +1300 [thread overview]
Message-ID: <48FEF85F.9020206@gentoo.org> (raw)
In-Reply-To: <200810220141.34728.cla@gentoo.org>
Dawid Węgliński wrote:
> Hello fellow developers and users.
>
> I'd like to know your opinion of bug #243050 [1]
>
> 01:18:59 cla @| If user bothers to patch his kernel, he can bother
> to add proper package.keyword line, imo.
++
> 01:21:52 hparker @| Or maybe get the patches added to gentoo-sources
or ++
maybe we can get the pm's to implement this as EAPI="999,999,999.99"
I suggest a syntax of "virtual/kernel:::::::user_patched"
On a more serious note, How can we confirm a package is stable when we
can't confirm the kernel it depends on is?
I would have no problem with gentoo-sources also including a use flag(s)
( or not ) and having it add patches to support software we have within
the tree. I have no say in that tho.
Alistair
next prev parent reply other threads:[~2008-10-22 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 23:41 [gentoo-dev] Keyword policy for non standard things Dawid Węgliński
2008-10-22 9:54 ` Alistair Bush [this message]
2008-10-22 10:43 ` Dawid Węgliński
2008-10-22 15:28 ` [gentoo-dev] " Christian Faulhammer
2008-10-22 21:12 ` Duncan
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=48FEF85F.9020206@gentoo.org \
--to=ali_bush@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