public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Video4Linux and linux headers
Date: Mon, 18 Apr 2005 14:27:08 -0400	[thread overview]
Message-ID: <200504181427.08126.vapier@gentoo.org> (raw)
In-Reply-To: <200504181157.11349@enterprise.flameeyes.is-a-geek.org>

On Monday 18 April 2005 05:56 am, Diego 'Flameeyes' Pettenò wrote:
> On Monday 18 April 2005 04:04, Mike Frysinger wrote:
> > this probably falls along side the USE refactoring someone else suggested
> > where we use.mask everything in base/use.mask that is arch-specific and
> > only unmask in appropriate profiles
>
> So what?

so what -> in other words, we should do this together instead of 1 USE flag at 
a time :P

> This, imho, should be done also for alsa and oss (just to take 
> media useflags which I'm more used to handle), which are linux (and
> obsd/nbsd, in case of oss) specific.
>
> I can get a list of flags to mask/unmask, if this is feasible, and commit
> them in the next days, cleaning up deps.

if by commit you mean the profiles then i think you should go make a list of 
specific USE flags and drop it onto the gentoo-dev list before committing :p
-mike

-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-04-18 18:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18  0:07 [gentoo-dev] Video4Linux and linux headers Diego 'Flameeyes' Pettenò
2005-04-18  2:04 ` Mike Frysinger
2005-04-18  9:56   ` Diego 'Flameeyes' Pettenò
2005-04-18 18:27     ` Mike Frysinger [this message]
2005-04-19 19:57       ` Diego 'Flameeyes' Pettenò
2005-04-19 20:16         ` Mike Frysinger
2005-04-20 11:46           ` Diego 'Flameeyes' Pettenò
2005-04-20 12:20             ` Jan Kundrát
2005-04-19 23:06         ` Greg KH
2005-04-19 23:31           ` Mike Frysinger

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=200504181427.08126.vapier@gentoo.org \
    --to=vapier@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